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

Re: [Pharo-project] clone vs shallowCopy

by Lukas Renggli

> where do you see that it is morphic related for me clone is only implemented > on character, Boolean, Object, SMalltInt symbol, UndefinedObject I am wrong. Forget what I said about #clone. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 12, 2010

Re: [Pharo-project] Pharo core and Seaside 3.0

by Miguel Enrique CobÃ¡ Martinez

El mar, 12-01-2010 a las 19:25 +0100, Lukas Renggli escribiÃ³: > > And also the class side install methods of Gofer please. > > > > Lets clean the way for Gofer as downloader/installer, Metacello as > > package management tools. > > These are examples to demonstrate how gofer works. They are not > supposed to be called for loading stuff. > > I am just using them all the time to keep my images up to date :-) But for some users they are causing confusion, given the current soup of install tools. If you don't mind, I really delete them or at least put a big advise in the comment to not use them because any momento will be outdated and maybe linking to the metacello instructions. You can always keep use them if you know they are correct for you. What do you think? > > Lukas > > -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 12, 2010

[Pharo-project] NewCompiler load on PharoCore

by Miguel Enrique CobÃ¡ Martinez

Hi Markus, what is the correct way to load NewCompiler in a PharoCore image. I am loading with: Gofer it squeaksource: 'NewCompiler'; package: 'NewCompiler'; load. But it has dependencies on SmaCCParserError. Then looking at the NewCompilerLoader >> loadPackages loadPackages self loadLatestPackage: 'AST-Core' from: 'http://www.squeaksource.com/rb/'. " self loadLatestPackage: 'SmaCC-' from: 'http://www.squeaksource.com/SmaccDevelopment/'. self loadLatestPackage: 'NewParser-' from: 'http://www.squeaksource.com/AST/'." self loadLatestPackage: 'NewCompiler-' from: 'http://www.squeaksource.com/NewCompiler/'. "Preferences setPreference: #compileUseNewCompiler toValue: true. Compiler recompileAll." "no, not working yet" so this are all the dependencies? Has NewCompiler teste on PharoCore? Is there a gofer script to load it? Or better a Metacello configuration? If you can give me the dependencies I can create the Metacello configuration. Right now I am creating the configurations for Magma and through WriteBarrier, they depend on NewCompiler. Thanks -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 12, 2010

Re: [Pharo-project] clone vs shallowCopy

by Nicolas Cellier

2010/1/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > http://code.google.com/p/pharo/issues/list?thanks=1789 > > I do not understand why we need deepCopy and why deepCopy does not implement the veryDeepCopy semantics? > > On Jan 12, 2010, at 1:41 PM, Levente Uzonyi wrote: > IMO it's the historical st80 deepCopy. Nicolas >>> - #copy is the normal copy operation. It should be used by default and >>> never overridden. It calls #postCopy that can be overridden to have >>> class specific copy semantics. >>> >>> - #shallowCopy does a shallow copy. It should never be overridden and >>> only be used if you want to get these very specific semantics. >>> >>> - #deepCopy does a deep copy. It should never be overridden and only >>> be used if you want to get these very specific semantics. >> >> It doesn't handle cycles, #veryDeepCopy does. >> >>> >>> - #clone comes from eToys and Morphic (AFAIK). It implements some >>> other copy semantics than #copy. I don't think that anybody should >>> call this method, other than code that depends on this particular copy >>> behavior. >>> >> >> From Morphic. >> >> >> Levente >> >>> This is exactly the same problematic as with #=. There can't be just >>> one #=. Other clients might consider other things when comparing >>> objects. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 12, 2010

Re: [Pharo-project] Where is BytecodeGenerator class?

by StÃ©phane Ducasse

pay attention that the newcompiler is under rewrite to work with closures and to replace the current one :) On Jan 12, 2010, at 7:16 PM, Miguel Enrique CobÃ¡ Martinez wrote: > El mar, 12-01-2010 a las 11:58 -0600, Miguel Enrique CobÃ¡ Martinez > escribiÃ³: >> Does somebody knows what package the class BytecodeGenerator is part of? >> >> I am loading WriteBarrier-pmm.26 from >> >> squeaksource.com/WriteBarrier.html and >> squeaksource.com/Magma.html >> >> and has references to BytecodeGenerator >> >> Thanks > > Responding to myself, google says that is part of NewCompiler. > > > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 12, 2010

Re: [Pharo-project] Pharo core and Seaside 3.0

by Lukas Renggli

> And also the class side install methods of Gofer please. > > Lets clean the way for Gofer as downloader/installer, Metacello as > package management tools. These are examples to demonstrate how gofer works. They are not supposed to be called for loading stuff. I am just using them all the time to keep my images up to date :-) Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 12, 2010

Re: [Pharo-project] clone vs shallowCopy

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=1790 > basicShallowCopy was a workaround for some badly written copy in > OrderedCollection. > I did add it, then removed it in squeak/trunk. I suggest following the > same path in Pharo.

Jan. 12, 2010

Re: [Pharo-project] clone vs shallowCopy

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/list?thanks=1789 I do not understand why we need deepCopy and why deepCopy does not implement the veryDeepCopy semantics? On Jan 12, 2010, at 1:41 PM, Levente Uzonyi wrote: >> - #copy is the normal copy operation. It should be used by default and >> never overridden. It calls #postCopy that can be overridden to have >> class specific copy semantics. >> >> - #shallowCopy does a shallow copy. It should never be overridden and >> only be used if you want to get these very specific semantics. >> >> - #deepCopy does a deep copy. It should never be overridden and only >> be used if you want to get these very specific semantics. > > It doesn't handle cycles, #veryDeepCopy does. > >> >> - #clone comes from eToys and Morphic (AFAIK). It implements some >> other copy semantics than #copy. I don't think that anybody should >> call this method, other than code that depends on this particular copy >> behavior. >> > > From Morphic. > > > Levente > >> This is exactly the same problematic as with #=. There can't be just >> one #=. Other clients might consider other things when comparing >> objects.

Jan. 12, 2010

Re: [Pharo-project] clone vs shallowCopy

by StÃ©phane Ducasse

On Jan 12, 2010, at 1:20 PM, Lukas Renggli wrote: > - #copy is the normal copy operation. It should be used by default and > never overridden. It calls #postCopy that can be overridden to have > class specific copy semantics. > > - #shallowCopy does a shallow copy. It should never be overridden and > only be used if you want to get these very specific semantics. > > - #deepCopy does a deep copy. It should never be overridden and only > be used if you want to get these very specific semantics. > > - #clone comes from eToys and Morphic (AFAIK). It implements some > other copy semantics than #copy. I don't think that anybody should > call this method, other than code that depends on this particular copy > behavior. we should copy that in Object class comment and all the methods where do you see that it is morphic related for me clone is only implemented on character, Boolean, Object, SMalltInt symbol, UndefinedObject > > This is exactly the same problematic as with #=. There can't be just > one #=. Other clients might consider other things when comparing > objects. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 12, 2010

Re: [Pharo-project] clone vs shallowCopy

by StÃ©phane Ducasse

> Hi, >>> >>> I found the clone primitive method in the Object class. >>> Its behavior looks the same as shallowCopy. Actually, shallowCopy just >>> sends basicShallowCopy wich calls the same primitive as clone >>> (primitive 148). >>> >> >> I wonder what image do you use. In a standard image #clone is primitive >> only, while #shallowCopy tries to copy the object if the primitive fails. >> #basicShallowCopy doesn't exist. >> > > I am using #clone, to be 100% sure that i cloning object primitively, > without additional logic, which #shallowCopy may introduce. shallowCopy should not overriden this is postCopy that should. how can you be sure that clone is not overriden? I have the same code for shallowCopy and clone and it would make sense to remove one and may to add that this methods should not be overridden (except by system classes) Stef

Jan. 12, 2010