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

Re: [Pharo-project] Monticello connecting to ftp repo on non-standard port

by Pat Maddox

On Mon, Jun 15, 2009 at 6:25 AM, Damien Cassou<damien.cassou(a)gmail.com> wrote: > On Mon, Jun 15, 2009 at 3:22 PM, Pat Maddox<pat.maddox(a)gmail.com> wrote: >> Image # is 10324. Â vm is squeak 4.11beta2u downloaded from the pharo >> site. Â I don't know how to copy and paste the log trace. Â When I click >> Open from MC the error window comes up. Â If I try to select text from >> there (which works in squeak, afaik) it brings up the debugger. Â From >> there I can see the trace but can't copy and paste it. Â What am I >> missing? > > you should check for a debug.log file Alright, here's the log for a few frames back. I think that should be enough, please let me know if you need more info MessageNotUnderstood: ByteArray>>port: 15 June 2009 6:29:29 am VM: Mac OS - intel - 1057 - Squeak3.8.1 of '28 Aug 2006' [latest update: #6747] Squeak VM 4.1.1b2 Image: Pharo0.1 [Latest update: #10324] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /Users/padillac/code/dogadopt Trusted Dir /foobar/tooBar/forSqueak/bogus Untrusted Dir /Users/padillac/Library/Preferences/Squeak/Internet/My Squeak ByteArray(Object)>>doesNotUnderstand: #port: Receiver: #[173 45 239 88] Arguments and temporary variables: aMessage: port: 47682 exception: MessageNotUnderstood: ByteArray>>port: resumeValue: nil Receiver's instance variables: #[173 45 239 88] Socket>>connectTo:port: Receiver: a Socket[unconnected] Arguments and temporary variables: hostAddress: #[173 45 239 88] port: 47682 Receiver's instance variables: semaphore: a Semaphore() socketHandle: #[254 248 53 74 0 0 0 0 144 91 48 22] readSemaphore: a Semaphore() writeSemaphore: a Semaphore() primitiveOnlySupportsOneSemaphore: false FTPClient>>openDataSocket:port: Receiver: a FTPClient Arguments and temporary variables: remoteHostAddress: #[173 45 239 88] dataPort: 47682 Receiver's instance variables: stream: SocketStream[inbuf:4kb/outbuf:4kb] connectInfo: a Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-metan...etc... lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).' pendingResponses: nil progressObservers: nil responseCode: 227 dataSocket: a Socket[unconnected] FTPClient>>openPassiveDataConnection Receiver: a FTPClient Arguments and temporary variables: portInfo: '173,45,239,88,186,66' list: an OrderedCollection('173' '45' '239' '88' '186' '66') dataPort: 47682 remoteHostAddress: #[173 45 239 88] Receiver's instance variables: stream: SocketStream[inbuf:4kb/outbuf:4kb] connectInfo: a Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-metan...etc... lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).' pendingResponses: nil progressObservers: nil responseCode: 227 dataSocket: a Socket[unconnected] FTPClient>>getDirectory Receiver: a FTPClient Arguments and temporary variables: dirList: nil Receiver's instance variables: stream: SocketStream[inbuf:4kb/outbuf:4kb] connectInfo: a Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-metan...etc... lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).' pendingResponses: nil progressObservers: nil responseCode: 227 dataSocket: a Socket[unconnected]

June 15, 2009

Re: [Pharo-project] Monticello connecting to ftp repo on non-standard port

by Damien Cassou

On Mon, Jun 15, 2009 at 3:22 PM, Pat Maddox<pat.maddox(a)gmail.com> wrote: > Image # is 10324. Â vm is squeak 4.11beta2u downloaded from the pharo > site. Â I don't know how to copy and paste the log trace. Â When I click > Open from MC the error window comes up. Â If I try to select text from > there (which works in squeak, afaik) it brings up the debugger. Â From > there I can see the trace but can't copy and paste it. Â What am I > missing? you should check for a debug.log file -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 15, 2009

Re: [Pharo-project] CompiledMethod and MethodReference

by StÃ©phane Ducasse

On Jun 15, 2009, at 3:12 PM, Alexandre Bergel wrote: >> I was playing with compiledMethod and MethodReference and it would be >> great if they could be more >> polymorphic: >> >> MethodReference>>methodClass >> ^ self actualClass > > > It will probably not do any harm, but why should a MethodReference be > polymorphic with a compiled method? like that we have a better system with less iskindof and methodClass vs. actualClass a MethodReference is a kind of wrapper for compiled method at the level of the tools so we would all gain having a good intersection between the two. > >> I was also thinking that it would be nice to have the package >> associated with the MethodReference >> eg: >> >> (Character>>#escapeEntities) package >> >> -> PackageInfo-Base >> >> What do you think about that? > > Good improvement > +1 > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 15, 2009

Re: [Pharo-project] Monticello connecting to ftp repo on non-standard port

by Pat Maddox

Image # is 10324. vm is squeak 4.11beta2u downloaded from the pharo site. I don't know how to copy and paste the log trace. When I click Open from MC the error window comes up. If I try to select text from there (which works in squeak, afaik) it brings up the debugger. From there I can see the trace but can't copy and paste it. What am I missing? Pat On Mon, Jun 15, 2009 at 6:12 AM, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> wrote: > can you tell us the > exact image number + vm + the log trace? > > Stef > > On Jun 15, 2009, at 3:10 PM, Pat Maddox wrote: > >> actually scratch that, Pharo's monticello just isn't working on FTP >> for me, even if the server is on port 21 >> >> On Mon, Jun 15, 2009 at 6:04 AM, Pat Maddox<pat.maddox(a)gmail.com> >> wrote: >>> Hi, I set up a monticello repository on one of my FTP servers. Â The >>> FTP server does not run on port 21. Â I created a repo connection from >>> my Pharo 09.06.1 image, it looks like: >>> >>> MCFtpRepository >>> Â Â Â Â host: 'mysite.com:1234' >>> Â Â Â Â directory: 'mc' >>> Â Â Â Â user: 'smalltalk' >>> Â Â Â Â password: 'supersecret' >>> >>> When I click on "Open" I get the error: >>> MessageNotUnderstood: ByteArray>>port: >>> >>> Any ideas what's going on? Â These connection settings work fine on a >>> Squeak image that I downloaded a few weeks ago. >>> >>> I would post a more complete stack trace but I can't figure out how. >>> I can open the debugger, but not copy and paste any stack trace >>> output. >>> >>> Pat >>> >> >> >> >> -- >> (415) 297-8028 >> http://www.patmaddox.com >> Twitter: @patmaddox >> GitHub: http://github.com/pat-maddox >> >> _______________________________________________ >> 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 > -- (415) 297-8028 http://www.patmaddox.com Twitter: @patmaddox GitHub: http://github.com/pat-maddox

June 15, 2009

Re: [Pharo-project] CompiledMethod and MethodReference

by Alexandre Bergel

> I was playing with compiledMethod and MethodReference and it would be > great if they could be more > polymorphic: > > MethodReference>>methodClass > ^ self actualClass It will probably not do any harm, but why should a MethodReference be polymorphic with a compiled method? > I was also thinking that it would be nice to have the package > associated with the MethodReference > eg: > > (Character>>#escapeEntities) package > > -> PackageInfo-Base > > What do you think about that? Good improvement +1 Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 15, 2009

Re: [Pharo-project] Monticello connecting to ftp repo on non-standard port

by StÃ©phane Ducasse

can you tell us the exact image number + vm + the log trace? Stef On Jun 15, 2009, at 3:10 PM, Pat Maddox wrote: > actually scratch that, Pharo's monticello just isn't working on FTP > for me, even if the server is on port 21 > > On Mon, Jun 15, 2009 at 6:04 AM, Pat Maddox<pat.maddox(a)gmail.com> > wrote: >> Hi, I set up a monticello repository on one of my FTP servers. The >> FTP server does not run on port 21. I created a repo connection from >> my Pharo 09.06.1 image, it looks like: >> >> MCFtpRepository >> host: 'mysite.com:1234' >> directory: 'mc' >> user: 'smalltalk' >> password: 'supersecret' >> >> When I click on "Open" I get the error: >> MessageNotUnderstood: ByteArray>>port: >> >> Any ideas what's going on? These connection settings work fine on a >> Squeak image that I downloaded a few weeks ago. >> >> I would post a more complete stack trace but I can't figure out how. >> I can open the debugger, but not copy and paste any stack trace >> output. >> >> Pat >> > > > > -- > (415) 297-8028 > http://www.patmaddox.com > Twitter: @patmaddox > GitHub: http://github.com/pat-maddox > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 15, 2009

Re: [Pharo-project] Monticello connecting to ftp repo on non-standard port

by Pat Maddox

actually scratch that, Pharo's monticello just isn't working on FTP for me, even if the server is on port 21 On Mon, Jun 15, 2009 at 6:04 AM, Pat Maddox<pat.maddox(a)gmail.com> wrote: > Hi, I set up a monticello repository on one of my FTP servers. Â The > FTP server does not run on port 21. Â I created a repo connection from > my Pharo 09.06.1 image, it looks like: > > MCFtpRepository > Â Â Â Â host: 'mysite.com:1234' > Â Â Â Â directory: 'mc' > Â Â Â Â user: 'smalltalk' > Â Â Â Â password: 'supersecret' > > When I click on "Open" I get the error: > MessageNotUnderstood: ByteArray>>port: > > Any ideas what's going on? Â These connection settings work fine on a > Squeak image that I downloaded a few weeks ago. > > I would post a more complete stack trace but I can't figure out how. > I can open the debugger, but not copy and paste any stack trace > output. > > Pat > -- (415) 297-8028 http://www.patmaddox.com Twitter: @patmaddox GitHub: http://github.com/pat-maddox

June 15, 2009

[Pharo-project] Monticello connecting to ftp repo on non-standard port

by Pat Maddox

Hi, I set up a monticello repository on one of my FTP servers. The FTP server does not run on port 21. I created a repo connection from my Pharo 09.06.1 image, it looks like: MCFtpRepository host: 'mysite.com:1234' directory: 'mc' user: 'smalltalk' password: 'supersecret' When I click on "Open" I get the error: MessageNotUnderstood: ByteArray>>port: Any ideas what's going on? These connection settings work fine on a Squeak image that I downloaded a few weeks ago. I would post a more complete stack trace but I can't figure out how. I can open the debugger, but not copy and paste any stack trace output. Pat

June 15, 2009

Re: [Pharo-project] Fwd: [Squeak-fr] durationToRun

by StÃ©phane Ducasse

Tx! Stef On Jun 15, 2009, at 10:43 AM, Nicolas Cellier wrote: > Sauf si la nouvelle version de Duration prend garde d'avoir nanos < > NanosInSecond > Ce qu'elle fait dans certains messages de crÃ©ation mais pas dans tous. > > Unless new version of Duration takes care to assert nanos < > NanosInSecond > Which is done in some instance creation messages but not all... > > I guess the reason of the changes were to avoid LargeInteger > operations and gain some efficiency. > It might not be the best idea to revert to a slow implementation. > We should better correct instance creation to always assert nanos < > NanosInSecond. > > Nicolas > > Le 15 juin 2009 10:06, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> a > Ã©crit : >> >> >> Begin forwarded message: >> >>> From: StÃ©phane Rollandin <hepta(a)zogotounga.net> >>> Date: June 15, 2009 9:32:54 AM CEDT >>> To: Squeak in french / Squeak en franÃ§ais <squeak-fr(a)lists.squeakfoundation.org >>>> >>> Subject: Re: [Squeak-fr] durationToRun >>> Reply-To: Squeak in french / Squeak en franÃ§ais <squeak-fr(a)lists.squeakfoundation.org >>>> >>> >>> [3500 milliSeconds asDelay wait] durationToRun >>> >>> donne 0:00:00:00.3501 sur Squeak3.10.2, mais donne le format correct >>> 0:00:00:03.5 sur Squeak3.8.2. >>> >>> le problÃ¨me vient de >>> >>> Duration class>> >>> days: days hours: hours minutes: minutes seconds: seconds >>> nanoSeconds: nanos >>> >>> ^ self seconds: ((days * SecondsInDay) >>> + (hours * SecondsInHour) >>> + (minutes * SecondsInMinute) >>> + seconds) >>> nanoSeconds: nanos >>> >>> >>> ... qui est faux, car les nanoseconds ne participent pas au calcul >>> des seconds. >>> >>> la version prÃ©cÃ©dente est: >>> >>> days: days hours: hours minutes: minutes seconds: seconds >>> nanoSeconds: nanos >>> >>> ^ self nanoSeconds: >>> ( ( (days * SecondsInDay) >>> + (hours * SecondsInHour) >>> + (minutes * SecondsInMinute) >>> + seconds ) * NanosInSecond ) >>> + nanos. >>> >>> >>> et lÃ Ã§a marche. >>> >>> Stef >>> >>> >>> _______________________________________________ >>> Squeak-fr mailing list >>> Squeak-fr(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/squeak-fr >>> >> >> >> _______________________________________________ >> 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 >

June 15, 2009

Re: [Pharo-project] Fwd: [Squeak-fr] durationToRun

by Nicolas Cellier

Sauf si la nouvelle version de Duration prend garde d'avoir nanos < NanosInSecond Ce qu'elle fait dans certains messages de crÃ©ation mais pas dans tous. Unless new version of Duration takes care to assert nanos < NanosInSecond Which is done in some instance creation messages but not all... I guess the reason of the changes were to avoid LargeInteger operations and gain some efficiency. It might not be the best idea to revert to a slow implementation. We should better correct instance creation to always assert nanos < NanosInSecond. Nicolas Le 15 juin 2009 10:06, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> a Ã©crit : > > > Begin forwarded message: > >> From: StÃ©phane Rollandin <hepta(a)zogotounga.net> >> Date: June 15, 2009 9:32:54 AM CEDT >> To: Squeak in french / Squeak en franÃ§ais <squeak-fr(a)lists.squeakfoundation.org >> > >> Subject: Re: [Squeak-fr] durationToRun >> Reply-To: Squeak in french / Squeak en franÃ§ais <squeak-fr(a)lists.squeakfoundation.org >> > >> >> [3500 milliSeconds asDelay wait] durationToRun >> >> donne 0:00:00:00.3501 sur Squeak3.10.2, mais donne le format correct >> 0:00:00:03.5 sur Squeak3.8.2. >> >> le problÃ¨me vient de >> >> Duration class>> >> days: days hours: hours minutes: minutes seconds: seconds >> nanoSeconds: nanos >> >> Â Â Â ^ self seconds: ((days * SecondsInDay) >> Â Â Â + (hours * SecondsInHour) >> Â Â Â + (minutes * SecondsInMinute) >> Â Â Â + seconds) >> Â Â Â Â Â Â Â nanoSeconds: nanos >> >> >> ... qui est faux, car les nanoseconds ne participent pas au calcul >> des seconds. >> >> la version prÃ©cÃ©dente est: >> >> days: days hours: hours minutes: minutes seconds: seconds >> nanoSeconds: nanos >> >> Â Â Â ^ self nanoSeconds: >> Â Â Â ( ( (days * SecondsInDay) >> Â Â Â + (hours * SecondsInHour) >> Â Â Â + (minutes * SecondsInMinute) >> Â Â Â + seconds ) * NanosInSecond ) >> Â Â Â + nanos. >> >> >> et lÃ Ã§a marche. >> >> Stef >> >> >> _______________________________________________ >> Squeak-fr mailing list >> Squeak-fr(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/squeak-fr >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 15, 2009