- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 1.1] #11422

by Mariano Martinez Peck

On Mon, Mar 14, 2011 at 4:27 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Mar 14, 2011, at 4:17 PM, Mariano Martinez Peck wrote: > > Marcus, should we build a Pharo 1.1.2 (dev) or it doesn't make sense? > > Can you do that withput changing *what* is installed? that is, keep the > versions > identical to the 1.1.1 dev image? > > I am sure that if we load newer ones, we will have problems and definitly > not the > energy to fix them. > > Yes, exactrly, I was refering to install exactly the same packages and versions as 1.1 but just in that core. It should be Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project version: '1.1') perform: #silently: with: true; perform: #load. but anyway I am not sure if it is worth it spending time on it...I just asked...but now I regret hahahaha > Marcus > > > > On Mon, Mar 14, 2011 at 2:56 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > >> 11422 >> ----- >> >> Release 1.1.2 >> >> >> Zip file for archive: >> >> https://gforge.inria.fr/frs/download.php/28341/PharoCore-1.1.2.zip >> >> >> ... this is 1.1.1 with some additional fixes >> -> fixes from Netstyle they did after moving to 1.1 >> -> some workarounds to get the tests green (on the build server) >> >> This is more for completeness, the new stable is 1.2. >> >> Marcus >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

March 14, 2011

Re: [Pharo-project] [update 1.1] #11422

by Marcus Denker

On Mar 14, 2011, at 4:17 PM, Mariano Martinez Peck wrote: > Marcus, should we build a Pharo 1.1.2 (dev) or it doesn't make sense? > Can you do that withput changing *what* is installed? that is, keep the versions identical to the 1.1.1 dev image? I am sure that if we load newer ones, we will have problems and definitly not the energy to fix them. Marcus > On Mon, Mar 14, 2011 at 2:56 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 11422 > ----- > > Release 1.1.2 > > > Zip file for archive: > > https://gforge.inria.fr/frs/download.php/28341/PharoCore-1.1.2.zip > > > ... this is 1.1.1 with some additional fixes > -> fixes from Netstyle they did after moving to 1.1 > -> some workarounds to get the tests green (on the build server) > > This is more for completeness, the new stable is 1.2. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 14, 2011

Re: [Pharo-project] Issue 3806 in pharo: Duration>>hours is broken

by Brent Pinkney

Hi, Lets end this thread quickly - I don't think it warrants a flame war. I took a hard line on the "toddler" bit as there is a tendency for some, often new members in the community to jump to conclusions about what is a pretty elegent platform (Squeak), and presume oversight or errors by default. Hence the "bona fide..." bit :) Further, arguments starting with "...everyone knows X..." is just not a reasonable starting point, post Enlightenment and outside theocracies. Many things about date and time libraries are just not obvious, which is why by Java 1.2 they already had 6 different date/time classes (if I recall). A better approach is to enquire as to why something is the way it is. By way of example, the loose consensus at the time was to follow the draft ANSI spec only, rather than pay ANSI to "get our spec back". Hell, my initials are all over the code, just ask. Cheers Brent the Tolerant and Approachable

March 14, 2011

Re: [Pharo-project] [update 1.1] #11422

by Mariano Martinez Peck

Marcus, should we build a Pharo 1.1.2 (dev) or it doesn't make sense? On Mon, Mar 14, 2011 at 2:56 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > 11422 > ----- > > Release 1.1.2 > > > Zip file for archive: > > https://gforge.inria.fr/frs/download.php/28341/PharoCore-1.1.2.zip > > > ... this is 1.1.1 with some additional fixes > -> fixes from Netstyle they did after moving to 1.1 > -> some workarounds to get the tests green (on the build server) > > This is more for completeness, the new stable is 1.2. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

March 14, 2011

Re: [Pharo-project] [ANN 1.3] prebuilt 1.3#13091 Core

by Mariano Martinez Peck

yes, uploadting to gforge is important, even if we have hudson ;) On Mon, Mar 14, 2011 at 3:25 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > > https://gforge.inria.fr/frs/download.php/28342/PharoCore-1.3-13091.zip > > ... to have a checkpoint in the archive. > > For everything else, it's better to load from Hudson: > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/ > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

March 14, 2011

Re: [Pharo-project] Issue 3815 in pharo: Filing in Class comments raises an error

by pharo＠googlecode.com

Comment #12 on issue 3815 by ryd...(a)gmail.com: Filing in Class comments raises an error http://code.google.com/p/pharo/issues/detail?id=3815 IMHO, yes. Stef is much closer and scarier, and do not seem to think so though :)

March 14, 2011

Re: [Pharo-project] [update 1.2 Core] #12341

by Alexandre Bergel

+1 Alexandre On 14 Mar 2011, at 11:28, Tudor Girba wrote: > Excellent! > > Doru > > > On 14 Mar 2011, at 13:56, Marcus Denker wrote: > >> 12341 >> ----- >> >> Release 1.2 (Core) >> >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> > > -- > www.tudorgirba.com > > "Presenting is storytelling." > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 14, 2011

Re: [Pharo-project] Issue 3817 in pharo: make Object >> error: deprecated

by pharo＠googlecode.com

Comment #3 on issue 3817 by guillerm...(a)gmail.com: make Object >> error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 I don't fully agree. You have to use particular exception types, when you want to give them a special treatment (by code). Most of the times, the error just flows to the user, where the only important thing is the message or the information the exception carries to show them to him. And that is the normal treatment, not an special one.

March 14, 2011

Re: [Pharo-project] Issue 3806 in pharo: Duration>>hours is broken

by pharo＠googlecode.com

Comment #11 on issue 3806 by ryd...(a)gmail.com: Duration>>hours is broken http://code.google.com/p/pharo/issues/detail?id=3806 My 2c: I agree with cesar: - Keep ANSI compliancy for #hours. - Add #asHours, doing what OP expected. - Explain the difference in comments, so noone thinks the implementer didn't know what he was doing :) #asSeconds is already ANSI, though the draft of the standard I have states it should include fractional parts. I suppose nanos instvar was added after the method was written, either way it should be extended to reflect the current situation. I suggest implementing #asHours and #asMinutes including fractions too, to keep it consistent.

March 14, 2011

Re: [Pharo-project] [update 1.2 Core] #12341

by Tudor Girba

Excellent! Doru On 14 Mar 2011, at 13:56, Marcus Denker wrote: > 12341 > ----- > > Release 1.2 (Core) > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- www.tudorgirba.com "Presenting is storytelling."

March 14, 2011