May 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] What's new in Pharo 5.0

by Sean P. DeNigris

Sean P. DeNigris wrote > Is there a more complete description than the announcement? I should've mentioned that I did see the link to the bugtracker, but I'm looking for some middle ground between the 5 bullet points in the announcement and the 2400+ issues tagged for Pharo 5.0 ----- Cheers, Sean -- View this message in context: http://forum.world.st/What-s-new-in-Pharo-5-0-tp4896954p4896955.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 24, 2016

What's new in Pharo 5.0

by Sean P. DeNigris

Is there a more complete description than the announcement? I've been dutifully following the mailing lists, but don't feel like I have a real handle on what the new features are and why they matter. Thanks! ----- Cheers, Sean -- View this message in context: http://forum.world.st/What-s-new-in-Pharo-5-0-tp4896954.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 24, 2016

Re: [Pharo-dev] compiledcode ?

by stepharo

Thanks and a nice one please :) Le 23/5/16 Ã 07:18, ClÃ©ment Bera a Ã©crit : > I will do a slice today. > > > On Mon, May 23, 2016 at 12:49 AM, Nicolai Hess <nicolaihess(a)gmail.com > <mailto:nicolaihess@gmail.com>> wrote: > > Would it be possible to add some comments, please. > > CompiledMethod is now a subclass of the new class CompiledCode > (and there is another > class CompiledBlock). > > Can we please don't add new classes at this system level without > *any* comment. > > nicolai > >

May 23, 2016

Re: [Pharo-dev] cleaning the Pharo Catalog

by stepharo

esteban we should sit with Pavel & christophe because package validation for distribution is on Pavel's roadmap and this is probably the time to activate it. Stef Le 23/5/16 Ã 09:53, Esteban Lorenzano a Ã©crit : > Hi guys, > > I will update the Catalog for Pharo 6 and I was wondering if we should keep the âUnsortedâ categoryâ¦ this corresponds with projects present in old MetacelloRepository repo, I added it at the beginning because I did not want those project to be lost, but in fact they are more or less abandonware and definitively, they were not very well kept (no descriptions, no tags and even worst, many of them will not load fine). > So what do you think? should I keep them? > > Esteban >

May 23, 2016

UTF-8 regression in package saving

by stepharo

Hi I did not have the time to check but it seems that people cannot save code with accents using Monticello. Stef

May 23, 2016

microsecondClockValue

by Eliot Miranda

Hi All, I see that access to the microsecond clock is called "microsecondClockValue". This name is wrong. It derives from millisecondClockValue which was indeed a value. The millisecond clock started from zero on every image startup and wrapped around every 45 days or so. The microsecond clock is quite different; it is an absolute clock whose zero is midnight on January 1st 1901, the start of the 20th century (damn those monks). So "Value" should be omitted from the selector. In Squeak we provide both Time utcMicrosecondClock and Time localMicrosecondClock which provide the number of microseconds since the start of 1/1/1901 in utc and local time zones respectively. It wraps round no sooner than 24/4/20168 (/not/ 2168). Time millisecondClockValue is provided for backward compatibility. _,,,^..^,,,_ best, Eliot

May 23, 2016

[pharo-project/pharo-core]

by GitHub

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

May 23, 2016

[pharo-project/pharo-core] 756471: 60029

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 7564717887459079fffd8bdf40f4ae6b69bd3a58 https://github.com/pharo-project/pharo-core/commit/7564717887459079fffd8bdf… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-23 (Mon, 23 May 2016) Changed paths: A Kernel.package/Boolean.class/instance/controlling/xor_.st M Manifest-Core.package/extension/TBehavior/instance/isManifest.st M Refactoring-Critics.package/RBDetectIfNoneRule.class/README.md M Refactoring-Critics.package/RBDetectIfNoneRule.class/instance/accessing/name.st M Refactoring-Critics.package/RBDetectIfNoneRule.class/instance/accessing/rationale.st M Refactoring-Critics.package/RBSmalltalkGlobalsRule.class/instance/accessing/name.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60028.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60029.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60028.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60029.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60029 18309 Typo in RBSmalltalkGlobalsRule https://pharo.fogbugz.com/f/cases/18309 18308 "Replaces detect:ifNone: by anySatisfy:" misleading rationale https://pharo.fogbugz.com/f/cases/18308 18247 deprecation warning on #isManifest for metaclasses https://pharo.fogbugz.com/f/cases/18247 18079 Boolean>>xor https://pharo.fogbugz.com/f/cases/18079 http://files.pharo.org/image/60/60029.zip

May 23, 2016

ConfigurationOfMerlin: to the guy who used a Halt as a cool way to let a message

by Esteban Lorenzano

donât! Iâm banning your configuration from MetaRepo because wellâ¦ it messes with the update process. yes, I could and will add more solid support, but seriously, this is very bad programming. Esteban

May 23, 2016

Re: [Pharo-dev] cleaning the Pharo Catalog

by Ben Coman

On Mon, May 23, 2016 at 4:04 PM, Cyril Ferlicot Delbecque <cyril.ferlicot(a)gmail.com> wrote: > > > On 23/05/2016 10:00, Stephan Eggermont wrote: >> Split into two categories? Those with full descriptions likely to load >> and those probably needing some updates? >> > > I like this option. Two tabs. A tab "PharoX" and a tab "Legacy" could be > an idea. But there are different levels of legacy. Once version back maybe not so bad. Several versions back likely worse. So maybe Pharo6, Pharo5, Legacy ? And it might be nice for Legacy to indicate which version Pharo they were associated with, but probably not enough value for such effort. cheers -ben > >> Stephan >> >> >> > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France >

May 23, 2016