October 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] scriptloader>>loadComanche

by Damien Cassou

On Tue, Oct 20, 2009 at 9:15 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Damien I would really like to see Universes coming back. Do we have > any chance getting it back? No, not in the sense of what was the previous Universes system. What we really want: - a repository on SqueakSource - a package in that repository with a single class - this class defines one method per package we support - each method as a small script to load the package (best thing for the method would be to load the loader of the particular package and launch it) -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Oct. 20, 2009

Re: [Pharo-project] scriptloader>>loadComanche

by Johan Brichau

On 20 Oct 2009, at 12:00, Torsten Bergmann wrote: >> We clearly need a universe like tools so that people can publish and >> maintain their add-ons. > > Yes, but we should be pragmatic for Seaside since it is the "flagship" > until we have the infrastructur set up. > > Maybe we should delete it from the core but we can the loading support > in the dev images. What do you all think? I just loaded metacello and used its seaside configuration to load the 3.0-alpha5 of seaside. It hits the 'reading a number failed' bug in 10487-DEV ...argh... ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

Oct. 20, 2009

[Pharo-project] Detecting overriding class extensions

by Simon Denier

Does anybody have a tool to detect class extensions which override methods? Because that's so bad it's evil. -- Simon

Oct. 20, 2009

[Pharo-project] [update] #11003 and 11004

by StÃ©phane Ducasse

11003 ----- Issue 1272: Strange copy return values for some SequenceableCollection subclasses Issue 1272: Strange copy return values for some SequenceableCollection subclasses - Part 2 Stef and Jorge

Oct. 20, 2009

Re: [Pharo-project] '' asNumber -> 'Reading a number failed'

by Esteban Lorenzano

+1 On 2009-10-20 08:35:17 -0200, csrabak(a)bol.com.br said: > I don't see where are we willing to arrive at. > > '' asNumber gives zero in several other Smalltalks (Dolphin and VW, > for example) and used to work as Mariano mentions in earlier versions > of Pharo (which makes me surmise is the way Squeak worked as well). > > So attempting addressing Nicolas point: the context where '' can be > expected is when reading text from some other source (mainly text from > a file) into you Pharo application. > > A library API has to have a reasonable balance between an excruciating > "conceptual right" set of calls and the "principle of minimum > surprise" for the corner cases in general. > > From this discussion, are we saying that for now on in order to have > strings converted into numbers if we want to have the behaviour '' > returning zero we shall change from '' asNumber to '' asNumberOrZero > and this method will call a more general method like this? > > Number>>asNumberOrZero > ^self asNumberOr: 0 > > And > > Number>>asNumberOr: aNumber > ^Number readFrom: self ifFail: [^aNumber] > > Just my .0199999.... > > > > > Em 20/10/2009 05:26, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> escreveu: >> I like asNumberOrZero we could have asNumberOr: aNumber so that we >> are not bound to Zero and I would include it. Now what the others >> think? Stef >> On Oct 20, 2009, at 4:31 AM, Nicolas Cellier wrote: >> >>> 2009/10/20 Mariano Martinez Peck : >>>> >>>> On Mon, Oct 19, 2009 at 10:33 PM, Nicolas Cellier wrote: >>>>> Yes, I understand the paradigm, nil is nothing is zero, empty is >>>>> nothing is zero... But frankly, do you think '' forms a valid >>>>> Number ? In every context ? So yes, this is expected, and can >>>>> break compatibility, but sometimes this is necessary. >>>>> If you want to keep this behaviour, you have to use an explicit >>>>> rule like: asNumberOrZero ^Number readFrom: self ifFail: [^0] >>>>> >>>> Thanks Nicolas. Now, the question is, do you think we can create >>>> this method in String as part of Pharo core? or I should add it >>>> to my application? >>>> cheers >>>> mariano >>>> >>> Depends if the pattern was used by many packages or not... It >>> would be stupid to create 10x the same extension to work around a >>> pharo change. Would it be a temporary helper subject to >>> deprecation, or a definitive feature ? I can't tell, and i don't >>> decide, i only suggest. >>> Nicolas >>> >>>>> Hope this helps... >>>>> Nicolas >>>>> 2009/10/20 Mariano Martinez Peck : >>>>>> Hi folks: In older images, like 10418, '' asNumber gave me a 0 >>>>>> (zero). But now, I get a 'Reading a number failed'. >>>>>> Is this expected? >>>>>> Perhaps it is due to the fix to this bug: >>>>>> >>>>>> http://code.google.com/p/pharo/issues/detail?can=1&q=1258&colspec=ID%20Type… any >>>>>> >>>>>> toughs? >>>>>> best >>>>>> Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 20, 2009

Re: [Pharo-project] #1339 - ODBC crashes vm

by Henrik Johansen

This one is caused by an initialization bug of some sort, the byteSizes of ODBC-structs are incorrect. In short, the solution is to do: ExternalStructure allSubclassesDo: [:each | each compileFields] after you load a package which defines ExternalStructure subclasses (like ODBC does). For some reason, in an image after loading: ExternalStrucure >> byteSize "Return the size in bytes of this structure." ^self compiledSpec first bitAnd: FFIStructSizeMask SQLHENV compiledSpec first: 65536 FFIStructSizeMask: 65535... So basically, when you allocate the struct a handle of a ByteArray of size byteSize, you'll sooner or later you access unallocated memory and crash. Recomputing all the compiledSpecs with the doit above leads to the correct sizes (4 in the case of SQLHENV) being stored in the compiledSpecs. Either way, not raising an error when the size for a struct when and'ed with the mask, but instead causing a silent crash later on just seems bad bad bad to me.

Oct. 20, 2009

Re: [Pharo-project] scriptloader>>loadComanche

by Adrian Lienhard

This afternoon we plan to start working on a package management system based on Metacello. It shouldn't be much work as the only missing part is a catalogue with metadata about the projects we selected. The project will provide the Metacello configurations that define the loading. Torsten, as far as I understand there exists a Metacello definition for Seaside 3 that should allow you to automatically load Seaside replacing the ScriptLoader definition. If not, we will see what we can do alternatively to make Seaside 3 loadable in the meantime (like providing a script based on Gofer (which is in the core now)). Adrian On Oct 20, 2009, at 12:00 , Torsten Bergmann wrote: >> #loadSeaside30 does not work anymore > > Ohh ... not again! > >> ScriptLoader should not be used for loading external packages :) > > We already had this discussion and agreed that we at least > keep the Seaside loading since "ScriptLoader loadSeaside30" > is widely communicated already! > >> We clearly need a universe like tools so that people can publish and >> maintain their add-ons. > > Yes, but we should be pragmatic for Seaside since it is the "flagship" > until we have the infrastructur set up. > > Maybe we should delete it from the core but we can the loading support > in the dev images. What do you all think? > > Bye > T. > > > > > -- > Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! > http://portal.gmx.net/de/go/dsl02 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 20, 2009

Re: [Pharo-project] '' asNumber -> 'Reading a number failed'

by csrabak＠bol.com.br

I don't see where are we willing to arrive at. '' asNumber gives zero in several other Smalltalks (Dolphin and VW, for example) and used to work as Mariano mentions in earlier versions of Pharo (which makes me surmise is the way Squeak worked as well). So attempting addressing Nicolas point: the context where '' can be expected is when reading text from some other source (mainly text from a file) into you Pharo application. A library API has to have a reasonable balance between an excruciating "conceptual right" set of calls and the "principle of minimum surprise" for the corner cases in general. >From this discussion, are we saying that for now on in order to have strings converted into numbers if we want to have the behaviour '' returning zero we shall change from '' asNumber to '' asNumberOrZero and this method will call a more general method like this? Number>>asNumberOrZero ^self asNumberOr: 0 And Number>>asNumberOr: aNumber ^Number readFrom: self ifFail: [^aNumber] Just my .0199999.... Em 20/10/2009 05:26, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> escreveu: > I like asNumberOrZero we could have asNumberOr: aNumber so that we > are not bound to Zero and I would include it. Now what the others > think? Stef > On Oct 20, 2009, at 4:31 AM, Nicolas Cellier wrote: > > > 2009/10/20 Mariano Martinez Peck : > >> > >> On Mon, Oct 19, 2009 at 10:33 PM, Nicolas Cellier wrote: > >>> Yes, I understand the paradigm, nil is nothing is zero, empty is > >>> nothing is zero... But frankly, do you think '' forms a valid > >>> Number ? In every context ? So yes, this is expected, and can > >>> break compatibility, but sometimes this is necessary. > >>> If you want to keep this behaviour, you have to use an explicit > >>> rule like: asNumberOrZero ^Number readFrom: self ifFail: [^0] > >>> > >> Thanks Nicolas. Now, the question is, do you think we can create > >> this method in String as part of Pharo core? or I should add it > >> to my application? > >> cheers > >> mariano > >> > > Depends if the pattern was used by many packages or not... It > > would be stupid to create 10x the same extension to work around a > > pharo change. Would it be a temporary helper subject to > > deprecation, or a definitive feature ? I can't tell, and i don't > > decide, i only suggest. > > Nicolas > > > >>> Hope this helps... > >>> Nicolas > >>> 2009/10/20 Mariano Martinez Peck : > >>>> Hi folks: In older images, like 10418, '' asNumber gave me a 0 > >>>> (zero). But now, I get a 'Reading a number failed'. > >>>> Is this expected? > >>>> Perhaps it is due to the fix to this bug: > >>>> > >>>> http://code.google.com/p/pharo/issues/detail?can=1&q=1258&colspec=ID%20Type… > >>>> any toughs? > >>>> best > >>>> Mariano

Oct. 20, 2009

[Pharo-project] scriptloader>>loadComanche

by Torsten Bergmann

>#loadSeaside30 does not work anymore Ohh ... not again! >ScriptLoader should not be used for loading external packages :) We already had this discussion and agreed that we at least keep the Seaside loading since "ScriptLoader loadSeaside30" is widely communicated already! >We clearly need a universe like tools so that people can publish and >maintain their add-ons. Yes, but we should be pragmatic for Seaside since it is the "flagship" until we have the infrastructur set up. Maybe we should delete it from the core but we can the loading support in the dev images. What do you all think? Bye T. -- Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! http://portal.gmx.net/de/go/dsl02

Oct. 20, 2009

Re: [Pharo-project] '' asNumber -> 'Reading a number failed'

by StÃ©phane Ducasse

I like asNumberOrZero we could have asNumberOr: aNumber so that we are not bound to Zero and I would include it. Now what the others think? Stef On Oct 20, 2009, at 4:31 AM, Nicolas Cellier wrote: > 2009/10/20 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >> >> On Mon, Oct 19, 2009 at 10:33 PM, Nicolas Cellier >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>> Yes, I understand the paradigm, nil is nothing is zero, empty is >>> nothing is zero... >>> But frankly, do you think '' forms a valid Number ? In every >>> context ? >>> So yes, this is expected, and can break compatibility, but sometimes >>> this is necessary. >>> >>> If you want to keep this behaviour, you have to use an explicit >>> rule like: >>> asNumberOrZero >>> ^Number readFrom: self ifFail: [^0] >>> >> >> Thanks Nicolas. Now, the question is, do you think we can create >> this method >> in String as part of Pharo core? or I should add it to my >> application? >> >> cheers >> >> mariano >> > > Depends if the pattern was used by many packages or not... > It would be stupid to create 10x the same extension to work around a > pharo change. > Would it be a temporary helper subject to deprecation, or a > definitive feature ? > I can't tell, and i don't decide, i only suggest. > > Nicolas > >>> >>> Hope this helps... >>> >>> Nicolas >>> >>> 2009/10/20 Mariano Martinez Peck <marianopeck(a)gmail.com>: >>>> Hi folks: In older images, like 10418, '' asNumber gave me a 0 >>>> (zero). >>>> But >>>> now, I get a 'Reading a number failed'. >>>> >>>> Is this expected? >>>> >>>> Perhaps it is due to the fix to this bug: >>>> >>>> >>>> http://code.google.com/p/pharo/issues/detail?can=1&q=1258&colspec=ID%20Type… >>>> >>>> any toughs? >>>> >>>> best >>>> >>>> Mariano >>>> >>>> _______________________________________________ >>>> 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

Oct. 20, 2009