- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [on] status of split join in pharo

by Oscar Nierstrasz

I have attempted to merge the functionality of Keith's Join package and Damien's and my RubyShards. The protocol is basically Keith's. Send splitOn: to a collection to split it, or send split: to the splitter with the collection as argument. The reverse messages are joinUsing: and join:. Everything has been generalized to work not only with Arrays and Strings but also OrderedCollections and SortedCollections. Not only sequences and blocks can be used as splitters, but also objects and regexes. Documentation is in SplitJoinTest on the class side, or see the class comment. See http://www.squeaksource.com/SplitJoin.html The latest version has been pushed into the PharoInbox. - on

April 12, 2009

[Pharo-project] linux version download problem

by Nicolas Cellier

I play the newbie again I'm interested in linux version I download stuff from http://www.pharo-project.org/download primary link: http://ftp.squeak.org/Exupery/vms/exupery-vm-0.15.1-linux.tz does not seem to integrate a ready-to-use squeak... (no plugin) it contains only a build directory with not much help to install (make does not work) alternative link: http://squeakvm.org/unix/release/Squeak-3.10-4.i686-pc-linux-gnu.tar.gz does have a simple INSTALL, but: $ squeak pharo0.1-10268dev09.04.1.image This interpreter (vers. 6502) cannot read image file (vers. 6504). Press CR to quit... Sorry to bother, but it's not usable Nicolas

April 12, 2009

Re: [Pharo-project] Integer>> numberOfDigits

by StÃ©phane Ducasse

:) decimalDigitLength looks like an obscure name. Stef On Apr 12, 2009, at 5:32 PM, Nicolas Cellier wrote: > Just two remarks from a non native english guy: > > 1) "digit" is also used with different semantic in #digitLength > #digitAt: #digitAt:put: > and thus a method comment is more than welcome! yeap! > > > 2) there is already a SmallInteger>>#decimalDigitLength doing what > you want. > However, since SmallInteger>>#numberOfDigitsInBase: is sending > #decimalDigitLength , > implementing : > Integer>>#decimalDigitLength > ^self numberOfDigitsInBase: 10 > is possible but a little troubling (inverted send logic in superclass > and subclass). > Also, you'd better not remove SmallInteger>>#decimalDigitLength > because avoiding quo: it is very efficient for most common cases. > So maybe adding a third message numberOfDigits is the best way... I > let you judge by yourself. > (Bad luck, I just come back from Greece, and if you ask an oracle, > answer is rarely yes or no). > > Nicolas > > 2009/4/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> may be there is a better solution.. 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 12, 2009

Re: [Pharo-project] Integer>> numberOfDigits

by Nicolas Cellier

Just two remarks from a non native english guy: 1) "digit" is also used with different semantic in #digitLength #digitAt: #digitAt:put: and thus a method comment is more than welcome! 2) there is already a SmallInteger>>#decimalDigitLength doing what you want. However, since SmallInteger>>#numberOfDigitsInBase: is sending #decimalDigitLength , implementing : Integer>>#decimalDigitLength ^self numberOfDigitsInBase: 10 is possible but a little troubling (inverted send logic in superclass and subclass). Also, you'd better not remove SmallInteger>>#decimalDigitLength because avoiding quo: it is very efficient for most common cases. So maybe adding a third message numberOfDigits is the best way... I let you judge by yourself. (Bad luck, I just come back from Greece, and if you ask an oracle, answer is rarely yes or no). Nicolas 2009/4/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > may be there is a better solution.. Nicolas?? > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 12, 2009

Re: [Pharo-project] [on] why can't I write on a WriteStream on an OrderedCollection?

by Nicolas Cellier

While I believe Nile is certainly a valuable work, it is very easy to patch old stream for this particular bug in the interim. http://bugs.squeak.org/view.php?id=2390 http://bugs.squeak.org/view.php?id=7269 http://bugs.squeak.org/view.php?id=7296 Nicolas 2009/4/12 Damien Cassou <damien.cassou(a)gmail.com>: > On Sat, Apr 11, 2009 at 7:39 PM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> wrote: >> Can anyone explain to me why this works fine: >> >> ((WriteStream on: (Array new)) nextPut: #foo) contents. >> >> but this doesn't? >> >> ((WriteStream on: (OrderedCollection new)) nextPut: #foo) contents. > > You should have listened when I presented Nile at ESUG some years ago :-) > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 12, 2009

Re: [Pharo-project] [on] why can't I write on a WriteStream on an OrderedCollection?

by Damien Cassou

On Sat, Apr 11, 2009 at 7:39 PM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> wrote: > Can anyone explain to me why this works fine: > > ((WriteStream on: (Array new)) nextPut: #foo) contents. > > but this doesn't? > > ((WriteStream on: (OrderedCollection new)) nextPut: #foo) contents. You should have listened when I presented Nile at ESUG some years ago :-) -- Damien Cassou http://damiencassou.seasidehosting.st

April 12, 2009

Re: [Pharo-project] Closure compiler

by Andreas Wacknitz

What about a simple (Squeak Smalltalk) compiler version 2 or compiler 2009? Some time in the future even this "new compiler" will probably an "old compiler" if Squeak survives long enough. Andreas Am 12.04.2009 um 10:50 schrieb StÃ©phane Ducasse: > OK > context taken into account. > > Suggestion > > Pluggable Compiler > Layered Compiler > > OpCode: the Smalltalk Open Compiler > > :) > > Stef > > On Apr 12, 2009, at 12:30 AM, Michael van der Gulik wrote: > >> On 4/12/09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> Oh yes it was appropriate I did not like simply the fact that you >>> could imply >>> that new compiler would be better named HannanCompiler since >>> people could understand that we were stealing things by not >>> mentioning >>> his name. >>> Now of course you may not have implied that and you may not like my >>> comment. >>> Still my point is clear. I'm greatfull to marcus to have resurrected >>> and maintained >>> this software over the years. >> >> I certainly didn't mean any disrespect or lack of admiration for what >> Marcus has done. It was just a name to avoid ambiguity. >> >> Do you have another suggestion for a name? >> >> Gulik. >> >> -- >> http://gulik.pbwiki.com/ >> >> _______________________________________________ >> 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 12, 2009

Re: [Pharo-project] Closure compiler

by StÃ©phane Ducasse

OK context taken into account. Suggestion Pluggable Compiler Layered Compiler OpCode: the Smalltalk Open Compiler :) Stef On Apr 12, 2009, at 12:30 AM, Michael van der Gulik wrote: > On 4/12/09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Oh yes it was appropriate I did not like simply the fact that you >> could imply >> that new compiler would be better named HannanCompiler since >> people could understand that we were stealing things by not >> mentioning >> his name. >> Now of course you may not have implied that and you may not like my >> comment. >> Still my point is clear. I'm greatfull to marcus to have resurrected >> and maintained >> this software over the years. > > I certainly didn't mean any disrespect or lack of admiration for what > Marcus has done. It was just a name to avoid ambiguity. > > Do you have another suggestion for a name? > > Gulik. > > -- > http://gulik.pbwiki.com/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 12, 2009

[Pharo-project] Integer>> numberOfDigits

by StÃ©phane Ducasse

may be there is a better solution.. Nicolas??

April 12, 2009

Re: [Pharo-project] Help fixing tests

by John M McIntosh

On 11-Apr-09, at 5:11 PM, Mariano Martinez Peck wrote: > Also there can be issues if things like File Handles are over- > allocated and you then rely on finalization to > fix things, which could interfere with things er it's hard to > explain, but once you see it, you know. > Technically this should not be a problem but as you see well something > is funky. I should clarify this, http://bugs.squeak.org/view.php?id=6434 But I see it's STILL an open issue in Pharo, not fixed in pharo0.1-10268dev09.04.1 http://code.google.com/p/pharo/issues/detail?id=517&q=6434&colspec=ID%20Typ… Ok, well let me ASSUME then the odd behavior you see is the result of this bug. -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

April 12, 2009