- Pharo-dev - lists.pharo.org

Re: [Pharo-project] OldSocket removal

by John M McIntosh

I should comment that the original method initializeNetworkIfError (whatever): was there because at the time (long ago) tcp/ip network support was an optional feature on macintosh and windows machines so there was fall back to support no network. That's unlikely today, and changing to just use the initializeNetwork is fine, where a thrown NetworkError would result in a valid sunit error. On Nov 13, 2008, at 7:26 AM, Dan Corneanu wrote: > I think it was not me. I have removed nothing from Network-Kernel. > We should use NetNameResolver class>>initializeNetwork. The method > throws a NetworkError if it can not initialize the network. > I think the method was never present in the pharo image. > -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Nov. 13, 2008

Re: [Pharo-project] OldSocket removal

by Dan Corneanu

I think it was not me. I have removed nothing from Network-Kernel. We should use NetNameResolver class>>initializeNetwork. The method throws a NetworkError if it can not initialize the network. I think the method was never present in the pharo image. How can I trace back changes made to the NetNameResolver class, without selecting each monticello version of Network and browsing the code inside it? On Wed, Nov 12, 2008 at 10:32 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi Dan, > > On Sat, Oct 25, 2008 at 8:36 PM, Dan Corneanu <dan.corneanu(a)gmail.com> wrote: >> I've played with the change sets from >> http://www.smalltalkconsulting.com/html/OTNotes4.html. >> I've made some changes to the tests, to fit the current Socket and >> NetNameResolver implementations. If it is of any help, I can put up a >> mcz so others can have a look to the code. > > John released a new changeset: > http://code.google.com/p/pharo/issues/detail?id=275. However, unit > tests does not run due to missing NetNameResolver > class>>initializeNetworkIfFail:. I think you removed that method. > Could you please check the changeset, make the necessary changes, > verify that all unit tests run and commit to PharoInbox? > > Also, please update the issue on google code according to what you do. > > Bye > > > -- > 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 >

Nov. 13, 2008

Re: [Pharo-project] OldSocket removal

by Dan Corneanu

I'll have a look. On Wed, Nov 12, 2008 at 10:32 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi Dan, > > On Sat, Oct 25, 2008 at 8:36 PM, Dan Corneanu <dan.corneanu(a)gmail.com> wrote: >> I've played with the change sets from >> http://www.smalltalkconsulting.com/html/OTNotes4.html. >> I've made some changes to the tests, to fit the current Socket and >> NetNameResolver implementations. If it is of any help, I can put up a >> mcz so others can have a look to the code. > > John released a new changeset: > http://code.google.com/p/pharo/issues/detail?id=275. However, unit > tests does not run due to missing NetNameResolver > class>>initializeNetworkIfFail:. I think you removed that method. > Could you please check the changeset, make the necessary changes, > verify that all unit tests run and commit to PharoInbox? > > Also, please update the issue on google code according to what you do. > > Bye > > > -- > 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 >

Nov. 13, 2008

Re: [Pharo-project] MNU addMakeSiblingHandle:

by StÃ©phane Ducasse

ok I will add that in the next release. This is strange since normally I did it in the update script. Stef On Nov 12, 2008, at 11:57 PM, nicolas cellier wrote: > > The halo button brings me a debugger : > Message not understood addMakeSiblingHandle: > > If that happens to you, just doIt: > Preferences resetHaloSpecifications. > > Nicolas > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 13, 2008

[Pharo-project] Rio renamed to File/Directory

by Keith Hodges

lets see how it goes Keith

Nov. 13, 2008

[Pharo-project] MNU addMakeSiblingHandle:

by nicolas cellier

The halo button brings me a debugger : Message not understood addMakeSiblingHandle: If that happens to you, just doIt: Preferences resetHaloSpecifications. Nicolas

Nov. 12, 2008

Re: [Pharo-project] About senders

by Lukas Renggli

> I would be happy to see a highlighting fixed, because sometimes it > highlights wrong portion of text instead of actual send. > Also, if look senders of #self. - in OB its not highligths text at all :( I fixed the highlighting a long time ago for OB-Refactory. Though, it is only used when triggering the search from the RB tools. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Nov. 12, 2008

Re: [Pharo-project] About senders

by David RÃ¶thlisberger

> I would be happy to see a highlighting fixed, because sometimes it > highlights wrong portion of text instead of actual send. > Also, if look senders of #self. - in OB its not highligths text at all :( yeah, I know, this should really get fixed. David > 2008/11/12 David RÃ¶thlisberger <squeak(a)webcitas.ch>: >>>> May be this was me but I often ask for senders and I get the implemented >>>> method. >>>> May be etoy curiving is driving crazy :) >>> Or your method is recursive :-) >> Probably it's that, because I never get the implementing method when I >> search for senders.

Nov. 12, 2008

Re: [Pharo-project] About senders

by Igor Stasenko

Yes, often, when you have a recursive calls , like: foo ^ super foo this method is sender and implementor both. But i don't see much problem with it. I would be happy to see a highlighting fixed, because sometimes it highlights wrong portion of text instead of actual send. Also, if look senders of #self. - in OB its not highligths text at all :( 2008/11/12 David RÃ¶thlisberger <squeak(a)webcitas.ch>: > >>> May be this was me but I often ask for senders and I get the implemented >>> method. >>> May be etoy curiving is driving crazy :) >> >> Or your method is recursive :-) > > Probably it's that, because I never get the implementing method when I > search for senders. > > > David > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Nov. 12, 2008

[Pharo-project] [update] #10146

by Marcus Denker

- Issue 219: Cryptography does not load into Pharo -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Nov. 12, 2008