- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Fwd: A UTC based implementation of DateAndTime

by Sven Van Caekenberghe

Pharo's DateAndTime is not the same as Squeak's. We are properly UTC based/aware, see #secondsSinceMidnightUTC and #julianDayNumberUTC. It is indeed perfectly possible to represent time using one number, but it will not be a SmallInteger. And depending on precision is will be a very large number. The split julian day number - seconds since midnight feels quite logical and practical to me. But yes, the 'date' concept is often confusing and difficult to handle in the light of timezones. To me, an old school, abstract Date object year/month/day would make sense. But then again, there are so many calendar systems, chronology is quite complicated. BasicJulianDate ? On 27 Aug 2014, at 01:10, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > From > http://forum.world.st/What-s-up-on-build-squeak-org-tp4760266p4760319.html : > > > David T. Lewis wrote >> I have been working on a variation of class DateAndTime that replaces its >> instance variables (seconds offset jdn nanos) with two instance variables, >> utcMicroseconds to represent microseconds elapsed since the Posix epoch, >> and >> localOffsetSeconds to represent the local time zone offset. When >> instantiating >> the time now, A single call primitiveUtcWithOffset is used to obtain these >> two values atomically as reported by the underlying platform. >> >> There are several advantages to this representation of DateAndTime, the >> most >> important of which is that its magnitude is unambiguous regardless of >> daylight >> savings transitions in local time zones. >> >> This is my attempt to address some historical baggage in Squeak. The VM >> reports time related to the local time zone, and the image attempts to >> convert to UTC (sometimes incorrectly). A UTC based representation makes >> the >> implementation of time zone tables more straightforward (see for example >> the Olson time zone tables in TimeZoneDatabase on SqueakMap). >> >> I am attaching the source code as a SAR file that can be loaded into a >> fully >> updated Squeak trunk image. The conversion process is slow, so be patient >> if you load it. >> >> This can be run on either an intepreter VM or Cog, but if you use Cog, >> please >> use a version dated June 2013 or later (the VM in the Squeak 4.5 >> all-in-one >> is fine). >> >> I am also attaching a copy of LXTestDateAndTimePerformance, which can be >> used to compare the performance of some basic DateAndTime functions. >> >> Performance of the UTC based DateAndTime is generally favorable compared >> to >> the original. Here is what I see on my system (smaller numbers are >> better). >> >> LXTestDateAndTimePerformance test results using the original Squeak >> DateAndTime >> on an interpreter VM: >> { >> #testNow->10143 . >> #testEquals->30986 . >> #testGreaterThan->80199 . >> #testLessThan->75912 . >> #testPrintString->10429 . >> #testStringAsDateAndTime->44657 >> } >> >> LXTestDateAndTimePerformance test results using the new UTC based >> DateAndTime >> on an interpreter VM: >> { >> #testNow->6423 . >> #testEquals->31625 . >> #testGreaterThan->22999 . >> #testLessThan->18514 . >> #testPrintString->12502 . >> #testStringAsDateAndTime->32912 >> } >> >> (CC to Brent Pinkney, author of the excellent Squeak Chronology package) >> >> Dave >> >> >> >> >> >> UtcDateAndTime-dtl.sar (40K) >> <http://forum.world.st/attachment/4760319/0/UtcDateAndTime-dtl.sar> >> LXTestDateAndTimePerformance.st (2K) >> <http://forum.world.st/attachment/4760319/1/LXTestDateAndTimePerformance.st> > > > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Fwd-A-UTC-based-implementation-of-DateAndTime-tp47749… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 27, 2014

Re: [Pharo-dev] Pharo Development Robustness (was: Why Bloc?)

by stepharo

Hi sean Thanks for this mail!!!! About bloc --------- I discussed with alain about this point at ESUG. Alain would like to finish the handlers and a couple of other points, clean everything and release a first version. The problem is that alain is often doing trial and changes. Here is where I think you can help: - turn some of the example for the layouts into tests - start to clean/revisit some basic morphs so that we can turn them into bloc counterparts easily. - I started to look at buttonMorph* - I started to rewrite MenuMorph because it is full of old code. I would like to remove the direct manipulation because it adds a lot of problems. If you want to join let me know. About TxText ------------ - Igor added morphs in text at ESUG and he was revisiting it yesterday. - we should make sure that the configuration is loading in 40 -now mocketry is loading in 40 so the configuration of TxText should be working. - we should check the current use of TextMorph and friends and use TxText Stef On 27/8/14 01:48, Sean P. DeNigris wrote: > The most important items on our IU Experience agenda - Tx and Bloc - are > totally reliant on two (brilliant, talented...) programmers while the rest > of the community hopes and waits. In no way to I lack appreciation for Alain > and Igor's efforts, but this does not seem like a robust or efficient use of > our manpower... So, I guess what I'm really asking for both projects is - > how can we help? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Pharo-Development-Robustness-was-Why-Bloc-tp4774980.h… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Aug. 27, 2014

Sprint 29/8 still planned?

by phil＠highoctane.be

Is there a sprint in Lille as announced a while ago? I'd be delighted to join :-) Phil

Aug. 27, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40191 Home: https://github.com/pharo-project/pharo-core

Aug. 27, 2014

[pharo-project/pharo-core] 2a94e5: 40191

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 2a94e5357858522cf92ecc51801bf64bd72812f8 https://github.com/pharo-project/pharo-core/commit/2a94e5357858522cf92ecc51… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-27 (Wed, 27 Aug 2014) Changed paths: M Gofer-Tests.package/GoferResource.class/instance/running/setUpMonticelloRepository.st A Metacello-TestsMCResources.package/MetacelloTestsMCPackage.class/instance/accessing/species.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script191.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40191.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40191 13911 Metacello test packages not properly unload https://pharo.fogbugz.com/f/cases/13911 http://files.pharo.org/image/40/40191.zip

Aug. 27, 2014

Looking for PhD students

by Michele Lanza

Dear all, this is an informal call for PhD students. Iâm Michele Lanza, head of the REVEAL research group from the University of Lugano in Switzerland, active in Smalltalk since many years (16 to be precise). The group, which you might know from tools like CodeCity, SpyWare, Softwarenaut, SPO, etc. and its involvement in Moose and Pharo in general, currently features 4 PhD students and 1 postdoc. 3 PhD students program with and in Pharo, namely Yuriy Tymchuk, Roberto Minelli, and Tommaso dal Sasso, who recently attended ESUG. Iâm looking for one or maybe even two PhD students. Topics with me are normally open and agreed upon by both sides, as long as itâs fun and relevant. I have some funky open topics. The only requirements are an open mind, good OO skills, the willingness to learn and to work hard. Drop me a line if youâre interested or know anyone whoâs interested. Thanks Michele BTW, I could say things about the nice climate in Lugano, the relatively good salary conditions, the generous available funding for traveling and hardware, etc. but if you come only for that you better stay away from me :-)

Aug. 27, 2014

Re: [Pharo-dev] PharoLauncher on Windows not the latest version

by kilon alios

I also downloaded the zip file it still does not give me the same version as MacOSX, no Pharo 4 template On Wed, Aug 27, 2014 at 11:04 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > I downloaded PharoLauncher from smalltalkhub for Windows and it appears is > not the latest version for example it has no template for downloading Pharo > 4. >

Aug. 27, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40190 Home: https://github.com/pharo-project/pharo-core

Aug. 27, 2014

[pharo-project/pharo-core] 2dfff4: 40190

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 2dfff429c4a2ace296f5c1a7168605c733984ae7 https://github.com/pharo-project/pharo-core/commit/2dfff429c4a2ace296f5c1a7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-27 (Wed, 27 Aug 2014) Changed paths: M AST-Core.package/RBLiteralArrayNode.class/instance/comparing/=.st M AST-Core.package/RBLiteralArrayNode.class/instance/comparing/equalTo_withMapping_.st M AST-Core.package/RBLiteralArrayNode.class/instance/private-replacing/replaceSourceWith_.st A NautilusRefactoring.package/NautilusRefactoring.class/instance/method/deprecateMethodFor_.st A NautilusRefactoring.package/NautilusRefactoring.class/instance/private-method/privateDeprecateMethodFor_.st M NautilusRefactoring.package/extension/ClassDescription/instance/methodRefactoring_.st M NautilusRefactoring.package/extension/TraitDescription/instance/methodRefactoring_.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/README.md A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/class/as yet unclassified/model_deprecateMethod_in_using_.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/definition.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/preconditions/preconditions.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/printing/storeOn_.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/deprecateMethod_in_using_.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/formDeprecatedMethod.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/formNewName.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/formOldName.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/formRewriteRule.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/transform.st A Refactoring-Core.package/RBMethod.class/instance/accessing/ast.st A Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/instance/accessing/someDemoMethod.st A Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/instance/initialize-release/classBlock_.st A Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/instance/initialize-release/newResultClass_.st A Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/instance/private/method_with_lots_of_arguments_.st A Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/README.md A Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/definition.st A Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/failure tests/testTooManyArguments.st A Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/failure tests/testWrongNumberOfArguments.st A Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethod.st A Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodOnClassSide.st A Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodWithLotsOfArguments.st A Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodWithSenders.st A Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodWithSendersInSubclass.st A Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testSenderNotSelf.st A Refactoring-Tests-Core.package/RBLintRuleTest.class/class/foo/someFooMethod.st A Refactoring-Tests-Core.package/RBLintRuleTest.class/class/foo/someOtherFooMethod.st A Refactoring-Tests-Core.package/RBLintRuleTest.class/instance/accessing/someOtherDemoMethod.st M Refactoring-Tests-Core.package/RBRenameMethodTest.class/instance/tests/testRenameTestMethod1.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script190.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40190.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A SmartSuggestions.package/SugsDeprecateMethod.class/README.md A SmartSuggestions.package/SugsDeprecateMethod.class/definition.st A SmartSuggestions.package/SugsDeprecateMethod.class/instance/accessing/label.st A SmartSuggestions.package/SugsDeprecateMethod.class/instance/execution/execute.st A SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createDeprecateMethod.st Log Message: ----------- 40190 13721 Failing test: RBRenameMethodTes>>#testRenameTestMethod1 https://pharo.fogbugz.com/f/cases/13721 13631 Deprecate method refactoring https://pharo.fogbugz.com/f/cases/13631 13916 RBLiteralArrayNode uses #to:do: instead of #with:do: (Coding Idiom Violation) https://pharo.fogbugz.com/f/cases/13916 http://files.pharo.org/image/40/40190.zip

Aug. 27, 2014

PharoLauncher on Windows not the latest version

by kilon alios

I downloaded PharoLauncher from smalltalkhub for Windows and it appears is not the latest version for example it has no template for downloading Pharo 4.

Aug. 27, 2014