- Pharo-dev - lists.pharo.org

Re: [Pharo-project] OldSocket removal

by Dan Corneanu

I have uploaded Network-DanCorneanu.50.mcz to pharoInbox. It fixes what I think it was a copy-paste error in Socket>>discardReceivedData.

Oct. 25, 2008

Re: [Pharo-project] How to find methods sent but not implemented?

by Marcus Denker

On 25.10.2008, at 12:49, Oscar Nierstrasz wrote: > > BTW, it would be cool to check this in the Pharo image. > > What would be the Smalltalk expression to pop open a browser on all > methods that send messages that are not implemented? (Or simply to > return a list of those messages?) > Yes, there is SystemNavigation>>#browseAllUnimplementedCalls The only problem is that it does not highlight the message that is detected. That can be a problem in large methods to find the problematic one. Marcus > - on > > On Oct 25, 2008, at 12:35, Adrian Lienhard wrote: > >> Probably, "literals do:" instead of "literalsDo:" will work. >> (Normally, methods to be removed should first be deprecated, which >> apparently was not done in this case.) >> >> Adrian >> >> On Oct 25, 2008, at 12:22 , Oscar Nierstrasz wrote: >> >>> >>> Hi, >>> >>> I was trying out the refactoring engine, and tried to run the code >>> critic. >>> >>> I got a message not understood in >>> SmalllintContext>>addLiteralsFor: which sends literalsDo: to its >>> argument aCompiledMethod. >>> >>> This appears to be the only method in the Pharo-dev image that >>> sends this msg. >>> >>> Any ida what the fix should be? >>> >>> - on >>> >>> >>> _______________________________________________ >>> 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 -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 25, 2008

Re: [Pharo-project] SmallLint broken -- no literalsDo: in CompiledMethod ?

by Marcus Denker

On 25.10.2008, at 12:35, Adrian Lienhard wrote: > Probably, "literals do:" instead of "literalsDo:" will work. > (Normally, methods to be removed should first be deprecated, which > apparently was not done in this case.) > Sorry, yes, I forgot to put in the deprecation... I will do that in the future. Marcus > Adrian > > On Oct 25, 2008, at 12:22 , Oscar Nierstrasz wrote: > >> >> Hi, >> >> I was trying out the refactoring engine, and tried to run the code >> critic. >> >> I got a message not understood in SmalllintContext>>addLiteralsFor: >> which sends literalsDo: to its argument aCompiledMethod. >> >> This appears to be the only method in the Pharo-dev image that >> sends this msg. >> >> Any ida what the fix should be? >> >> - on >> >> >> _______________________________________________ >> 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 -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 25, 2008

Re: [Pharo-project] SmallLint broken -- no literalsDo: in CompiledMethod ?

by StÃ©phane Ducasse

yes I will add a deprecated method. I do not know which changes did that. stef On Oct 25, 2008, at 12:35 PM, Adrian Lienhard wrote: > Probably, "literals do:" instead of "literalsDo:" will work. > (Normally, methods to be removed should first be deprecated, which > apparently was not done in this case.) > > Adrian > > On Oct 25, 2008, at 12:22 , Oscar Nierstrasz wrote: > >> >> Hi, >> >> I was trying out the refactoring engine, and tried to run the code >> critic. >> >> I got a message not understood in SmalllintContext>>addLiteralsFor: >> which sends literalsDo: to its argument aCompiledMethod. >> >> This appears to be the only method in the Pharo-dev image that >> sends this msg. >> >> Any ida what the fix should be? >> >> - on >> >> >> _______________________________________________ >> 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. 25, 2008

Re: [Pharo-project] How to find methods sent but not implemented?

by StÃ©phane Ducasse

unsentMessages or something like that is available. Stef On Oct 25, 2008, at 12:49 PM, Oscar Nierstrasz wrote: > > BTW, it would be cool to check this in the Pharo image. > > What would be the Smalltalk expression to pop open a browser on all > methods that send messages that are not implemented? (Or simply to > return a list of those messages?) > > - on > > On Oct 25, 2008, at 12:35, Adrian Lienhard wrote: > >> Probably, "literals do:" instead of "literalsDo:" will work. >> (Normally, methods to be removed should first be deprecated, which >> apparently was not done in this case.) >> >> Adrian >> >> On Oct 25, 2008, at 12:22 , Oscar Nierstrasz wrote: >> >>> >>> Hi, >>> >>> I was trying out the refactoring engine, and tried to run the code >>> critic. >>> >>> I got a message not understood in >>> SmalllintContext>>addLiteralsFor: which sends literalsDo: to its >>> argument aCompiledMethod. >>> >>> This appears to be the only method in the Pharo-dev image that >>> sends this msg. >>> >>> Any ida what the fix should be? >>> >>> - on >>> >>> >>> _______________________________________________ >>> 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. 25, 2008

[Pharo-project] How to find methods sent but not implemented?

by Oscar Nierstrasz

BTW, it would be cool to check this in the Pharo image. What would be the Smalltalk expression to pop open a browser on all methods that send messages that are not implemented? (Or simply to return a list of those messages?) - on On Oct 25, 2008, at 12:35, Adrian Lienhard wrote: > Probably, "literals do:" instead of "literalsDo:" will work. > (Normally, methods to be removed should first be deprecated, which > apparently was not done in this case.) > > Adrian > > On Oct 25, 2008, at 12:22 , Oscar Nierstrasz wrote: > >> >> Hi, >> >> I was trying out the refactoring engine, and tried to run the code >> critic. >> >> I got a message not understood in SmalllintContext>>addLiteralsFor: >> which sends literalsDo: to its argument aCompiledMethod. >> >> This appears to be the only method in the Pharo-dev image that >> sends this msg. >> >> Any ida what the fix should be? >> >> - on >> >> >> _______________________________________________ >> 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. 25, 2008

Re: [Pharo-project] SmallLint broken -- no literalsDo: in CompiledMethod ?

by Oscar Nierstrasz

Right, thanks. In an older Squeak image I find: CompiledMethod>>literalsDo: aOneArgumentBlock ^self literals do:aOneArgumentBlock. - on On Oct 25, 2008, at 12:35, Adrian Lienhard wrote: > Probably, "literals do:" instead of "literalsDo:" will work. > (Normally, methods to be removed should first be deprecated, which > apparently was not done in this case.) > > Adrian > > On Oct 25, 2008, at 12:22 , Oscar Nierstrasz wrote: > >> >> Hi, >> >> I was trying out the refactoring engine, and tried to run the code >> critic. >> >> I got a message not understood in SmalllintContext>>addLiteralsFor: >> which sends literalsDo: to its argument aCompiledMethod. >> >> This appears to be the only method in the Pharo-dev image that >> sends this msg. >> >> Any ida what the fix should be? >> >> - on >> >> >> _______________________________________________ >> 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. 25, 2008

Re: [Pharo-project] SmallLint broken -- no literalsDo: in CompiledMethod ?

by Adrian Lienhard

Probably, "literals do:" instead of "literalsDo:" will work. (Normally, methods to be removed should first be deprecated, which apparently was not done in this case.) Adrian On Oct 25, 2008, at 12:22 , Oscar Nierstrasz wrote: > > Hi, > > I was trying out the refactoring engine, and tried to run the code > critic. > > I got a message not understood in SmalllintContext>>addLiteralsFor: > which sends literalsDo: to its argument aCompiledMethod. > > This appears to be the only method in the Pharo-dev image that sends > this msg. > > Any ida what the fix should be? > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 25, 2008

[Pharo-project] SmallLint broken -- no literalsDo: in CompiledMethod ?

by Oscar Nierstrasz

Hi, I was trying out the refactoring engine, and tried to run the code critic. I got a message not understood in SmalllintContext>>addLiteralsFor: which sends literalsDo: to its argument aCompiledMethod. This appears to be the only method in the Pharo-dev image that sends this msg. Any ida what the fix should be? - on

Oct. 25, 2008

[Pharo-project] Fwd: [Etoys] Fully Relicensed version of mainstream Squeak

by StÃ©phane Ducasse

Begin forwarded message: > From: Yoshiki Ohshima <yoshiki(a)vpri.org> > Date: October 23, 2008 7:04:54 PM CEDT > To: stephane ducasse <stephane.ducasse(a)free.fr> > Cc: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > Subject: Re: [Etoys] Fully Relicensed version of mainstream Squeak > > At Thu, 23 Oct 2008 15:11:04 +0200, > stephane ducasse wrote: >> >> I could not see the authorship2 code. >> Did you send it? > > No, but I uploaded code to SqueakSource. > > http://www.squeaksource.com/MethodAuthorship/MethodAuthorship-yo.1.mcz > > is the data collection mechansim (I forgot to set the ancestor so the > version number of the mcz package is wrong) and the Seaside code is > > http://www.squeaksource.com/AuthorshipViewer.html > > -- Yoshiki >

Oct. 25, 2008