April 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Expectation for readFrom:... getting bored to fix bugs.

by csrabak＠bol.com.br

Then a more appropriate class would be ISO8601DateAndTime for this method to remain in Pharo? -- Cesar Rabak Em 24/04/2010 16:48, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com > escreveu: 2010/4/24 Julian Fitzell : > On Sat, Apr 24, 2010 at 10:54 AM, stephane ducasse > wrote: >> >> What are the expectation for DateAndTime>>readFrom? > > Personally, my expectation is that it doesn't exist. :) > > To believe that there is a single way of parsing strings into dates (or > numbers, or anything else) that will be appropriate in all cases is pretty > silly. It would seem much better to me to have configurable parsing classes. > > Julian > Sure, that might be usefull, however current implementation intention clearly seems related to http://en.wikipedia.org/wiki/ISO_8601 Nicolas > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 25, 2010

[Pharo-project] saving headless image on Mac

by Tudor Girba

Hi, I am trying to integrate a Pharo image into a continuous integration system through the command line. For that I need to spawn the image, do something, save and quit. The problem is that on Mac (using 4.2.2beta1U), when I open the resulting image I get a very tiny window instead of the original size. The command below reveals the problem (save-and-quite-image.st is attached): /Applications/Squeak4.2.2beta1U/Squeak\ 4.2.2beta1U.app/Contents/MacOS/ Squeak\ VM\ Opt -headless Pharo-1.0.image THE_PATH/save-and-quit- image.st Could anyone advise me how to proceed to get around this problem? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow."

April 24, 2010

Re: [Pharo-project] starting to think about 1.1 freeze

by Schwab,Wilhelm K

Not to be inflammatory, the weak collections have been broken all along. They are not thread safe, and so cannot hope to be adequately cleaned as objects are finalized. My efforts to compensate have been aimed at clearing away nils that are left behind. If the weak collection itself is busted (holds too strongly??), then my additions are not going to help. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Henrik Johansen Sent: Saturday, April 24, 2010 5:07 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] starting to think about 1.1 freeze WeakKeyDictionary, to be specific. To be frank, to me the new implementation in 1.1 seems simply broken. Cheers, Henry Den 24. apr. 2010 kl. 22.58 skrev "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu >: > Stef, > > What do you mean by "weak structures?" Weak collections? > > Bill > > > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo- > project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse > Sent: Saturday, April 24, 2010 3:58 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] starting to think about 1.1 freeze > > ok but this is still good to know what we could wrap up. > Now I'm fixing some tests if somebody wants to help there are some > problems on weak structures. > > Stef > On Apr 24, 2010, at 10:31 AM, Marcus Denker wrote: > >> >> On Apr 23, 2010, at 8:30 PM, Schwab,Wilhelm K wrote: >> >>> Stef, >>> >>> I will soon reach a point of missing a way to do callbacks. Alien/ >>> FFI is listed among the goals, and I would very much like to see >>> that happen, especially if callbacks are well supported as a result. >>> >> >> But what we should *not* do is to delay the release for that. >> Releases >> should be a snapshot of what is already done. 1.1 *as it is now* >> (minus bugs) is already a huge step forward. If we delay that to make >> it even better, we will again delay the release for a looong time. >> >> I vote for just defininf 1.1 as what 1.1 is *now* and stabilize it. >> There will be a 1.2 anyway. >> >> Marcus >> >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord >> Europe. Team RMoD. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 24, 2010

Re: [Pharo-project] starting to think about 1.1 freeze

by Henrik Johansen

WeakKeyDictionary, to be specific. To be frank, to me the new implementation in 1.1 seems simply broken. Cheers, Henry Den 24. apr. 2010 kl. 22.58 skrev "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu >: > Stef, > > What do you mean by "weak structures?" Weak collections? > > Bill > > > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo- > project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse > Sent: Saturday, April 24, 2010 3:58 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] starting to think about 1.1 freeze > > ok but this is still good to know what we could wrap up. > Now I'm fixing some tests if somebody wants to help there are some > problems on weak structures. > > Stef > On Apr 24, 2010, at 10:31 AM, Marcus Denker wrote: > >> >> On Apr 23, 2010, at 8:30 PM, Schwab,Wilhelm K wrote: >> >>> Stef, >>> >>> I will soon reach a point of missing a way to do callbacks. Alien/ >>> FFI is listed among the goals, and I would very much like to see >>> that happen, especially if callbacks are well supported as a result. >>> >> >> But what we should *not* do is to delay the release for that. >> Releases >> should be a snapshot of what is already done. 1.1 *as it is now* >> (minus bugs) is already a huge step forward. If we delay that to >> make it even better, we will again delay the release for a looong >> time. >> >> I vote for just defininf 1.1 as what 1.1 is *now* and stabilize it. >> There will be a 1.2 anyway. >> >> Marcus >> >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord >> Europe. Team RMoD. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 24, 2010

Re: [Pharo-project] starting to think about 1.1 freeze

by Schwab,Wilhelm K

Stef, What do you mean by "weak structures?" Weak collections? Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Saturday, April 24, 2010 3:58 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] starting to think about 1.1 freeze ok but this is still good to know what we could wrap up. Now I'm fixing some tests if somebody wants to help there are some problems on weak structures. Stef On Apr 24, 2010, at 10:31 AM, Marcus Denker wrote: > > On Apr 23, 2010, at 8:30 PM, Schwab,Wilhelm K wrote: > >> Stef, >> >> I will soon reach a point of missing a way to do callbacks. Alien/FFI is listed among the goals, and I would very much like to see that happen, especially if callbacks are well supported as a result. >> > > But what we should *not* do is to delay the release for that. Releases > should be a snapshot of what is already done. 1.1 *as it is now* (minus bugs) is already a huge step forward. If we delay that to make it even better, we will again delay the release for a looong time. > > I vote for just defininf 1.1 as what 1.1 is *now* and stabilize it. There will be a 1.2 anyway. > > Marcus > > > > -- > Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord > Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 24, 2010

Re: [Pharo-project] (Duration seconds: 73994 nanoSeconds: 321000000) seconds

by Alexandre Bergel

I commented on the website of google. Alexandre On 24 Apr 2010, at 13:59, StÃ©phane Ducasse wrote: > http://code.google.com/p/pharo/issues/detail?id=2352 > > I proposed a fix and would loved to have feedback. > > Stef > > On Apr 24, 2010, at 7:51 PM, StÃ©phane Ducasse wrote: > >> the problem seems to be due to >> (Duration seconds: 73994 nanoSeconds: 321000000) seconds >> which returns a fraction >> >> >> In pharo >> >> Duration>>seconds >> "Answer the number of seconds the receiver represents." >> >> ^ (seconds rem: SecondsInMinute) + (nanos / NanosInSecond) >> >> >> In Squeak>>seconds >> "Answer the number of seconds the receiver represents." >> >> ^seconds rem: SecondsInMinute >> >> >> Now I have the impression that the squeak version is right >> >> What do you think? >> >> Stef >> >> >> On Apr 24, 2010, at 4:38 PM, stephane ducasse wrote: >> >>> Hi guys >>> >>> I have to fix my house :) so I could not continue to kill this one >>> on Unstable 11321 >>> >>> '-1199-01-05T20:33:14.321-05:00' asDateAndTime printString >>> -> '-1199-01-05T20:33:(14321/1000).321-05:00' >>> >>> STef >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 24, 2010

Re: [Pharo-project] Expectation for readFrom:... getting bored to fix bugs.

by StÃ©phane Ducasse

What I did was to stick with the ISO parsing and added a fuzzy readfrom (the previous one in pharo) so that readFrom: read only iso but well and fuzzy tries to find its way with strange input. Stef On Apr 24, 2010, at 9:48 PM, Nicolas Cellier wrote: > 2010/4/24 Julian Fitzell <jfitzell(a)gmail.com>: >> On Sat, Apr 24, 2010 at 10:54 AM, stephane ducasse >> <stephane.ducasse(a)free.fr> wrote: >>> >>> What are the expectation for DateAndTime>>readFrom? >> >> Personally, my expectation is that it doesn't exist. :) >> >> To believe that there is a single way of parsing strings into dates (or >> numbers, or anything else) that will be appropriate in all cases is pretty >> silly. It would seem much better to me to have configurable parsing classes. >> >> Julian >> > > Sure, that might be usefull, however current implementation intention > clearly seems related to > http://en.wikipedia.org/wiki/ISO_8601 > > Nicolas > >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 24, 2010

Re: [Pharo-project] Expectation for readFrom:... getting bored to fix bugs.

by StÃ©phane Ducasse

yes but before having that and all the complexity it can bring I suggest to stick with a non fuzzy and customizable parser that does not exist yet and stick to ISO format and parse only this one but well. Stef On Apr 24, 2010, at 9:16 PM, Julian Fitzell wrote: > On Sat, Apr 24, 2010 at 10:54 AM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > What are the expectation for DateAndTime>>readFrom? > > Personally, my expectation is that it doesn't exist. :) > > To believe that there is a single way of parsing strings into dates (or numbers, or anything else) that will be appropriate in all cases is pretty silly. It would seem much better to me to have configurable parsing classes. > > Julian > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 24, 2010

Re: [Pharo-project] Expectation for readFrom:... getting bored to fix bugs.

by Nicolas Cellier

2010/4/24 Julian Fitzell <jfitzell(a)gmail.com>: > On Sat, Apr 24, 2010 at 10:54 AM, stephane ducasse > <stephane.ducasse(a)free.fr> wrote: >> >> What are the expectation for DateAndTime>>readFrom? > > Personally, my expectation is that it doesn't exist. :) > > To believe that there is a single way of parsing strings into dates (or > numbers, or anything else) that will be appropriate in all cases is pretty > silly. It would seem much better to me to have configurable parsing classes. > > Julian > Sure, that might be usefull, however current implementation intention clearly seems related to http://en.wikipedia.org/wiki/ISO_8601 Nicolas > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 24, 2010

Re: [Pharo-project] Expectation for readFrom:... getting bored to fix bugs.

by Julian Fitzell

On Sat, Apr 24, 2010 at 10:54 AM, stephane ducasse <stephane.ducasse(a)free.fr > wrote: > What are the expectation for DateAndTime>>readFrom? > Personally, my expectation is that it doesn't exist. :) To believe that there is a single way of parsing strings into dates (or numbers, or anything else) that will be appropriate in all cases is pretty silly. It would seem much better to me to have configurable parsing classes. Julian

April 24, 2010