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

Re: [Pharo-project] Issue 3499 in pharo: FixUnderscores (package & instructions) out of date

by pharo＠googlecode.com

Comment #12 on issue 3499 by sean.p.denigris: FixUnderscores (package & instructions) out of date http://code.google.com/p/pharo/issues/detail?id=3499 It seemed like the consensus is that FixUnderscores leads to code that's not properly versioned and should be removed from core. Why include instructions for something we don't want people to use?

Jan. 4, 2011

Re: [Pharo-project] Issue 3498 in pharo: remove:ifAbsent: in linked list leads to interruption/sync problems

by pharo＠googlecode.com

Comment #10 on issue 3498 by stephane.ducasse: remove:ifAbsent: in linked list leads to interruption/sync problems http://code.google.com/p/pharo/issues/detail?id=3498 adrian: I'll try that... But I still don't understand why the change in Pharo that makes LinkedList>>remove:ifAbsent: non thread safe can cause the problem since this code is executed by the timerEvent process, which runs at the highest priority. This process should never be suspended during the execution of remove:ifAbsent:. What do I miss? Andreas: The problem isn't thread-safety, at least in the classical definition. What happens is that if you're removing processes by using LinkedList>>remove: you are subject to a race condition where the semaphore gets signaled *while* you are removing the the process. Obviously, hillarity ensues at this point, which is why I made primitive suspend do the Right Thing (i.e., remove the process primitively). There are two parameters which affect if you're likely to see the effect or not: One is the number of suspension points (real sends) in the method. The more you have, the more likely you're affected. The second one is whether the method can tolerate having the process removed "underneith its feet". Both are far worse in Pharo.

Jan. 4, 2011

Re: [Pharo-project] Pharo and CommandShell on OSX ?

by StÃ©phane Ducasse

> > >> On Mon, Jan 03, 2011 at 06:55:45PM -0800, Stef T wrote: >>> 1) CommandShell complains about AioPlugin not being present and that it will use the 'old slow' way. That's fine, it's merely a warning >> >> AFAIK, noone has tried building the AioPlugin for Mac, so you will get this >> warning when running on a Mac. But as you say, it's just a warning. > > Is there a pointer for the source code ? I am pretty handy with Xcode and don't mind giving it a whirl ;) good there is a gitorious account for the vm and we would enjoy that people can contribute via there. http://gitorious.org/cogvm http://gitorious.org/squeak-vm > >> >>> but >>> 2) None of the commands get executed. If I try the stuff which will eval inside squeak/pharo, then that's fine (Eg; stdout nextPutAll: 'hello world'; cr.). However, if I try a command such as 'ls' or 'who', all hell breaks lose. stack trace follows :) >>> >>> If I am doing anything obviously wrong, please feel free to hit me over the head :) >> >> Nope, it's not you, it's the plugin included with your VM. Some >> of the Mac VMs in circulation were accidentally built with a very >> out of date version of the OSProcessPlugin. Apparently you have >> one of them, and it will definitely not work. But I think there >> is a newer version (4.2.5 IIRC) that has the up to date plugin >> that works properly on Mac. >> > > Hrm, I am using the OSProcess from squeaksource .59. The version history says > > Name: OSProcess-dtl.59 > Author: dtl > Time: 28 November 2010, 8:43:48.839 pm > UUID: bd5d2b4e-efbd-4091-ac0a-d0bd7af64b2c > > surely this is 'new enough' ? Is there a known 'stable' version you would suggest ? > > regards > S. > >> Dave >> >> >>> >>> Regards >>> S. >>> >>> >>> >>> >>> 3 January 2011 6:49:43 pm >>> >>> VM: Mac OS - intel - 1065 - Squeak3.8.1 of '28 Aug 2006' [latest update: #6747] Squeak VM 4.2.4b1 >>> Image: Pharo-1.1-11406-rc3 [Latest update: #11406] >>> >>> SecurityManager state: >>> Restricted: false >>> FileAccess: true >>> SocketAccess: true >>> Working Dir /Users/stef/squeak/SeaSide-3.0 >>> Trusted Dir /foobar/tooBar/forSqueak/bogus >>> Untrusted Dir /Users/stef/Library/Preferences/Squeak/Internet/My Squeak >>> >>> UndefinedObject(Object)>>mustBeBooleanIn: >>> Receiver: nil >>> Arguments and temporary variables: >>> context: BufferedAsyncFileReadStream>>moveAvailableDataFrom: >>> proceedValue: nil >>> Receiver's instance variables: >>> nil >>> >>> UndefinedObject(Object)>>mustBeBoolean >>> Receiver: nil >>> Arguments and temporary variables: >>> >>> Receiver's instance variables: >>> nil >>> >>> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >>> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >>> Arguments and temporary variables: >>> sqFile: #[48 205 236 155 72 91 120 160 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0] >>> bufferSize: 1000 >>> buffer: '...etc... >>> count: #(0) >>> Receiver's instance variables: >>> >>> >>> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >>> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >>> Arguments and temporary variables: >>> >>> Receiver's instance variables: >>> >>> >>> BufferedAsyncFileReadStream>>update: >>> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >>> Arguments and temporary variables: >>> aParameter: a PseudoAioEventHandler >>> Receiver's instance variables: >>> >>> >>> [] in PseudoAioEventHandler(Object)>>changed: >>> Receiver: a PseudoAioEventHandler >>> Arguments and temporary variables: >>> aParameter: BufferedAsyncFileReadStream: 'pipeReader' >>> aDependent: a PseudoAioEventHandler >>> Receiver's instance variables: >>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>> >>> DependentsArray>>do: >>> Receiver: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> Arguments and temporary variables: >>> aBlock: [:aDependent | aDependent update: aParameter] >>> dep: BufferedAsyncFileReadStream: 'pipeReader' >>> i: 1 >>> iLimiT: 1 >>> Receiver's instance variables: >>> a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> >>> PseudoAioEventHandler(Object)>>changed: >>> Receiver: a PseudoAioEventHandler >>> Arguments and temporary variables: >>> aParameter: a PseudoAioEventHandler >>> Receiver's instance variables: >>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>> >>> PseudoAioEventHandler(Object)>>changed >>> Receiver: a PseudoAioEventHandler >>> Arguments and temporary variables: >>> >>> Receiver's instance variables: >>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>> >>> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >>> Receiver: a PseudoAioEventHandler >>> Arguments and temporary variables: >>> d: a Delay(125 msecs) >>> Receiver's instance variables: >>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>> >>> BlockClosure>>repeat >>> Receiver: [self changed. >>> d wait] >>> Arguments and temporary variables: >>> >>> Receiver's instance variables: >>> outerContext: [] in PseudoAioEventHandler>>eventGeneratorProcess >>> startpc: 59 >>> numArgs: 0 >>> >>> [] in PseudoAioEventHandler>>eventGeneratorProcess >>> Receiver: a PseudoAioEventHandler >>> Arguments and temporary variables: >>> d: a Delay(125 msecs) >>> Receiver's instance variables: >>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>> >>> [] in BlockClosure>>newProcess >>> Receiver: [[self changed. >>> d wait] repeat] >>> Arguments and temporary variables: >>> >>> Receiver's instance variables: >>> outerContext: PseudoAioEventHandler>>eventGeneratorProcess >>> startpc: 54 >>> numArgs: 0 >>> >>> >>> --- The full stack --- >>> UndefinedObject(Object)>>mustBeBooleanIn: >>> UndefinedObject(Object)>>mustBeBoolean >>> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >>> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >>> BufferedAsyncFileReadStream>>update: >>> [] in PseudoAioEventHandler(Object)>>changed: >>> DependentsArray>>do: >>> PseudoAioEventHandler(Object)>>changed: >>> PseudoAioEventHandler(Object)>>changed >>> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >>> BlockClosure>>repeat >>> [] in PseudoAioEventHandler>>eventGeneratorProcess >>> [] in BlockClosure>>newProcess >>> >> > >

Jan. 4, 2011

Re: [Pharo-project] Pharo and CommandShell on OSX ?

by StÃ©phane Ducasse

On Jan 4, 2011, at 4:25 AM, David T. Lewis wrote: > On Mon, Jan 03, 2011 at 06:55:45PM -0800, Stef T wrote: >> Hello Everyone, >> So, long time squeaker, first time pharo(er ?). Please don't hold this against me ;) >> >> I am trying to get CommandShell loaded into Pharo (using the Seaside Image) via Monticello. I have tried this on Pharo 1.1/1.1.1/1.2 for the record (same thing). I skip past the MVC/Morphic errors about PluggableList etc, and I can get the command shell to pop-up, however, two things happen; >> > > The CommandShell package on SqueakSource is also now broken down > into sub-packages, so you can load the individual parts if you want. > But just proceding through the MVC warnings as you did is harmless. > >> 1) CommandShell complains about AioPlugin not being present and that it will use the 'old slow' way. That's fine, it's merely a warning > > AFAIK, noone has tried building the AioPlugin for Mac, so you will get this > warning when running on a Mac. But as you say, it's just a warning. I imagine that we will see that with igor and the automatic build too. > >> but >> 2) None of the commands get executed. If I try the stuff which will eval inside squeak/pharo, then that's fine (Eg; stdout nextPutAll: 'hello world'; cr.). However, if I try a command such as 'ls' or 'who', all hell breaks lose. stack trace follows :) >> >> If I am doing anything obviously wrong, please feel free to hit me over the head :) > > Nope, it's not you, it's the plugin included with your VM. Some > of the Mac VMs in circulation were accidentally built with a very > out of date version of the OSProcessPlugin. Apparently you have > one of them, and it will definitely not work. But I think there > is a newer version (4.2.5 IIRC) that has the up to date plugin > that works properly on Mac. > > Dave > > >> >> Regards >> S. >> >> >> >> >> 3 January 2011 6:49:43 pm >> >> VM: Mac OS - intel - 1065 - Squeak3.8.1 of '28 Aug 2006' [latest update: #6747] Squeak VM 4.2.4b1 >> Image: Pharo-1.1-11406-rc3 [Latest update: #11406] >> >> SecurityManager state: >> Restricted: false >> FileAccess: true >> SocketAccess: true >> Working Dir /Users/stef/squeak/SeaSide-3.0 >> Trusted Dir /foobar/tooBar/forSqueak/bogus >> Untrusted Dir /Users/stef/Library/Preferences/Squeak/Internet/My Squeak >> >> UndefinedObject(Object)>>mustBeBooleanIn: >> Receiver: nil >> Arguments and temporary variables: >> context: BufferedAsyncFileReadStream>>moveAvailableDataFrom: >> proceedValue: nil >> Receiver's instance variables: >> nil >> >> UndefinedObject(Object)>>mustBeBoolean >> Receiver: nil >> Arguments and temporary variables: >> >> Receiver's instance variables: >> nil >> >> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >> Arguments and temporary variables: >> sqFile: #[48 205 236 155 72 91 120 160 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0] >> bufferSize: 1000 >> buffer: '...etc... >> count: #(0) >> Receiver's instance variables: >> >> >> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >> Arguments and temporary variables: >> >> Receiver's instance variables: >> >> >> BufferedAsyncFileReadStream>>update: >> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >> Arguments and temporary variables: >> aParameter: a PseudoAioEventHandler >> Receiver's instance variables: >> >> >> [] in PseudoAioEventHandler(Object)>>changed: >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> aParameter: BufferedAsyncFileReadStream: 'pipeReader' >> aDependent: a PseudoAioEventHandler >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> DependentsArray>>do: >> Receiver: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> Arguments and temporary variables: >> aBlock: [:aDependent | aDependent update: aParameter] >> dep: BufferedAsyncFileReadStream: 'pipeReader' >> i: 1 >> iLimiT: 1 >> Receiver's instance variables: >> a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> >> PseudoAioEventHandler(Object)>>changed: >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> aParameter: a PseudoAioEventHandler >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> PseudoAioEventHandler(Object)>>changed >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> d: a Delay(125 msecs) >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> BlockClosure>>repeat >> Receiver: [self changed. >> d wait] >> Arguments and temporary variables: >> >> Receiver's instance variables: >> outerContext: [] in PseudoAioEventHandler>>eventGeneratorProcess >> startpc: 59 >> numArgs: 0 >> >> [] in PseudoAioEventHandler>>eventGeneratorProcess >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> d: a Delay(125 msecs) >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> [] in BlockClosure>>newProcess >> Receiver: [[self changed. >> d wait] repeat] >> Arguments and temporary variables: >> >> Receiver's instance variables: >> outerContext: PseudoAioEventHandler>>eventGeneratorProcess >> startpc: 54 >> numArgs: 0 >> >> >> --- The full stack --- >> UndefinedObject(Object)>>mustBeBooleanIn: >> UndefinedObject(Object)>>mustBeBoolean >> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >> BufferedAsyncFileReadStream>>update: >> [] in PseudoAioEventHandler(Object)>>changed: >> DependentsArray>>do: >> PseudoAioEventHandler(Object)>>changed: >> PseudoAioEventHandler(Object)>>changed >> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >> BlockClosure>>repeat >> [] in PseudoAioEventHandler>>eventGeneratorProcess >> [] in BlockClosure>>newProcess >> >

Jan. 4, 2011

Re: [Pharo-project] Issue 3505 in pharo: 1.2 Build fails: MetacelloProjectSpecLoadError: No version found for '1.0.2' of ConfigurationOfMemoryMonitor

by pharo＠googlecode.com

Comment #3 on issue 3505 by marianopeck: 1.2 Build fails: MetacelloProjectSpecLoadError: No version found for '1.0.2' of ConfigurationOfMemoryMonitor http://code.google.com/p/pharo/issues/detail?id=3505 yes, or point to the conf of MetacelloRepository and not the one of MemoryMonitor repo

Jan. 4, 2011

Re: [Pharo-project] Some questions about omnibroser framework

by StÃ©phane Ducasse

hi juan sebastien did you try to send this mail to the ob mailing-list? Stef On Jan 4, 2011, at 6:12 AM, aizcorbe wrote: > > I have been using the OmniBroser framework to extend the Lint browser > (OR2LintBrowser) and i found some strange behavior i would like to comment: > > 1) When you select an item in the browser, the metagraph define some edges > leading to other metanode types. This is translated sending the edge names > to the real nodes and getting all the following nodes, and then, those nodes > are displayed on the following column at the browser, and if there isn't a > next column it is created. The strange issue here is that, if the messages > for edge taking on the concrete nodes retrieves an empty collection of > nodes, the next column is created anyway, because for the browser there is a > next metagraph node. Is this a problem or not? (I had to define much more > complex metagraphs because of this, just to avoid an empty column). > > 2) When you use filters on the metagraph, they are applied over each taken > edge leading to the next metagraph. The filters are usually used for node > ordering and here is a problem. If you have more than one edge from the > current metanode, you will get a order filter applied over two different > edges and then, the order will be not ok, since there will be some partially > ordered concatenated node lists, and not just a fully ordered list. > > 3) Another issue is not about omnibrowser, but i think is worth to be noted. > If you extend any class in another package using *package-category protocol > for new or modified methods, you will see the extended class on the package > root, but you won't see it at the cathegory (i think it would be nice and a > little more clear seeing the extensions at the specific package-category). > Also i found that TestRunner do not put the unitTest classes under a package > unless the class itself where defined at the selected package (even if i > added some test using the *package-category protocol name) > > I hope some of you found this intresting > > cheers > > > -- > View this message in context: http://forum.world.st/Some-questions-about-omnibroser-framework-tp3173047p3… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 4, 2011

Re: [Pharo-project] next steps for pharo -- a suggestions on documentation

by StÃ©phane Ducasse

On Jan 4, 2011, at 12:15 AM, csrabak(a)bol.com.br wrote: > Last year (and IIRC before last year as well) we exchanged a set of clever stubs of code which created a collection of classes had not comments. > > Could we have one of these scripts run as a part of the process in Hudson for validations/QA of the core images (for starting the whole thing) and a statistic which would allow us to track our progress in the percentage of commented classes in core? yes if somebody can give a try to get some statistics this would be good. After we can check how we can push that in hudson > > -- > Cesar Rabak >

Jan. 4, 2011

Re: [Pharo-project] editing a method outside the image?

by StÃ©phane Ducasse

sergio may be you should explain us what you are trying to do? On Jan 3, 2011, at 11:07 PM, sergio_101 wrote: > one problem i having (in a long line).. > > is that my DateAndTime class >> now > > looks like this: > > now > ^ self basicNew > ticks: (Duration > days: SqueakEpoch > hours: 0 > minutes: 0 > seconds: self totalSeconds > nanoSeconds: MillisecondClockOffset milliSeconds * NanosInMillisecond) ticks > offset: self localOffset; > yourself > > the problem is, milliseconds is not defined anywhere.. this is there > as a remnant of sheduler.. > > i need to replace it with the REAL one: > > now > ^ self basicNew > ticks: (Array with: SqueakEpoch with: Time totalSeconds with: 0) > offset: self localTimeZone offset > > the problem is that when i try to update "now", i keep getting the > error for that it can't find "milliSeconds".. > > when i delete "now" and try to paste the correct one in.. i error out, too.. > > i think the snake is eating its tail.. > > can i replace the "now" method somehow with the image not running? > > thanks! > > -- > ---- > peace, > sergio > photographer, journalist, visionary > > http://www.CodingForHire.com > http://www.coffee-black.com > http://www.painlessfrugality.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 >

Jan. 4, 2011

Re: [Pharo-project] Crash on saving with Monticello

by StÃ©phane Ducasse

> > If it is possible in the startup script to check whether the libuuid installation is correct then the startup script could print an error message plus information on how to correct the installation. IMO, this would be better than either crashing after startup or hacking the image to avoid the primitive because of a platform error. The issue then is how to check. One straight-forward way would be for the start-up script to invoke a small C program that invoked libuuid in exactly the same way as the UUIDPlugin, and if this fails then the startup script can warn. The issue remains how to correct the installation once the error has been detected. > yes this sounds a good way to deal with it.

Jan. 4, 2011

Re: [Pharo-project] Crash on saving with Monticello

by StÃ©phane Ducasse

> Yep :) > > But I do want to make it clear that it seems the bug is not in > the plugin, it is in the libuuid implementations. We've all been > trying to find workarounds, but unfortunately not with much > success. For a while we could work around it by compiling the > plugin internally (which somehow prevents the bug from being > exposed), but now we have some 64-bit Linux distros that accidentally > left the 32-bit libuuid out of the distro, which prevents the VM > from running if the plugin was compiled internally. I'm sure it > has been fixed in up to date distros, but now we have one set of > Linux users with buggy libuuid libraries, and another set of Linux > users with missing 32-bit libuuid libraries, so somebody is going > to get screwed either way now :-/ ;( May be should put a large readme file somewhere explaining the situation. > > I'm sure there must be some way to fix this that we're all missing, > so if anyone wants to look at it with a fresh set of eyes that > would be great. > > Dave > >

Jan. 4, 2011