[Pharo-project] OSProcess in Pharo 2.0
Hi, I was trying to play with OSProcess. Simple goal, to execute $ ldconfig -p | grep libcairo.so and get the result as a string or stream. Several problems I met: - newest OSProcess loaded from its configuration depends on FileDirectory which is not present in Pharo 2.0. - when I fixed previous point I wondered how to get the output of a particular command. Damien P. told me I had to use the particular OSProcess of Coral or use CommandShell - I tried installing CommandShell but its configuration depends on PluggableTextView which is not in Pharo 2.0 - when I fixed previous point, I realized CommandShell depends even more on FileSystem and I didn't understand how to get the output stream - so I gave up with CommandShell and tried Coral's OSProcess - So I fixed some references to FileDirectory again but then many unit tests of OSProcess didn't pass so I felt uncomfortable At the end, Coral's OSProcess worked for me, but I don't know why all these tests are failing -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
[Pharo-project] OSProcess in Pharo 2.0
Hi, I'd like to script some shell commands in Pharo 2.0. Is there any way to do that in Pharo? It seems OSProcess class is suitable but seems it's not yet fully ported in Pharo 2.0. Thanks, Roberto
[Pharo-project] osprocess in pharo 2.0
Hi, For some reason I thought that OSProcess was integrated in Pharo 2.0, but it appears that it is not in the image. Did I understand the issue incorrectly, or was the class renamed to something else? If it is not in the image, was it already ported to SmalltalkHub? (I could not find it) I am asking because I would like to know if we should continue to load OSProcess explicitly with Moose. Cheers, Doru -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."
Re: [Pharo-project] OSProcess in Pharo 2.0
On 2012-10-30, at 10:15, Damien Cassou wrote: > Hi, > > I was trying to play with OSProcess. Simple goal, to execute > > $ ldconfig -p | grep libcairo.so > > and get the result as a string or stream. > > Several problems I met: > > - newest OSProcess loaded from its configuration depends on > FileDirectory which is not present in Pharo 2.0. Didn't have time yet to fix this: https://code.google.com/p/pharo/issues/detail?id=6740 > - when I fixed previous point I wondered how to get the output of a > particular command. Damien P. told me I had to use the particular > OSProcess of Coral or use CommandShell => PipeableOSProcess is your friend It works somehow, but in my experience is not that stable > - I tried installing CommandShell but its configuration depends on > PluggableTextView which is not in Pharo 2.0 > - when I fixed previous point, I realized CommandShell depends even > more on FileSystem and I didn't understand how to get the output > stream > - so I gave up with CommandShell and tried Coral's OSProcess > - So I fixed some references to FileDirectory again but then many unit > tests of OSProcess didn't pass so I felt uncomfortable > > At the end, Coral's OSProcess worked for me, but I don't know why all > these tests are failing > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >
Re: [Pharo-project] OSProcess in Pharo 2.0
Hi, I'm not up to speed on the latest Pharo, but I'll try to offer a couple of tips... On Tue, Oct 30, 2012 at 10:15:12AM +0100, Damien Cassou wrote: > Hi, > > I was trying to play with OSProcess. Simple goal, to execute > > $ ldconfig -p | grep libcairo.so > > and get the result as a string or stream. > > Several problems I met: > > - newest OSProcess loaded from its configuration depends on > FileDirectory which is not present in Pharo 2.0. Hopefully it will be possible to provide some kind of compatibility layer to deal with this. The CommandShell repository already has a CommandShellPharo package that I made in November 2010 to address menu registration changes in Pharo at that time. I have not tried to keep up with the Pharo 2.0 changes, but if a compatibility package is possible, this might be a good place to put it. > - when I fixed previous point I wondered how to get the output of a > particular command. Damien P. told me I had to use the particular > OSProcess of Coral or use CommandShell > - I tried installing CommandShell but its configuration depends on > PluggableTextView which is not in Pharo 2.0 I split the CommandShell package into subpackages in order to address this. I guess we need a ConfigurationOfCommandShell to handle this properly, but if you load the individual sub-packages (e.g. CommandShell-base and friends, instead of CommandShell which contains all of the subpackages), and omit the CommandShell-MVC package, then you will not have this problem. PluggableTextView is part of the MVC package (a command shell can be opened in either Morphic or MVC). HTH, Dave > - when I fixed previous point, I realized CommandShell depends even > more on FileSystem and I didn't understand how to get the output > stream > - so I gave up with CommandShell and tried Coral's OSProcess > - So I fixed some references to FileDirectory again but then many unit > tests of OSProcess didn't pass so I felt uncomfortable > > At the end, Coral's OSProcess worked for me, but I don't know why all > these tests are failing > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill
Re: [Pharo-project] OSProcess in Pharo 2.0
Is OSProcess still the best/correct way? I've been using it in 2.0. Seems to work. load: MCHttpRepository location: 'http://smalltalkhub.com/mc/dh83/fisleg/main' user: '' password: '' then do: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOSProcess'; load. (Smalltalk at: #ConfigurationOfOSProcess) project bleedingEdge load. Is the only issue updating to FileSystem, or are there other changes that are needed for Pharo 2.0? On Fri, Nov 9, 2012 at 9:35 AM, roberto.mine...@usi.ch wrote: > Hi, > > I'd like to script some shell commands in Pharo 2.0. > Is there any way to do that in Pharo? It seems OSProcess class is suitable > but seems it's not yet fully ported in Pharo 2.0. > > Thanks, > Roberto
Re: [Pharo-project] OSProcess in Pharo 2.0
both are right 1) OSProcess has not been fully ported to 2.0 2) you can load a compatibility package (the one of Camillo or FileDirectory package from the graveyard, http://smalltalkhub.com/#!/~Pharo/Graveyard20), and most probably will work fine in 2.0, since the OSProcess problems are due to the FileSystem replacement. and of course, if someone want to collaborate by doing OSProcess work fine in 2.0 without needing to load an obsolete package, that would be great :) Esteban On Nov 13, 2012, at 9:59 AM, "Peter H. Meadows" wrote: > Is OSProcess still the best/correct way? > > I've been using it in 2.0. Seems to work. > > load: > > MCHttpRepository > location: 'http://smalltalkhub.com/mc/dh83/fisleg/main' > user: '' > password: '' > > then do: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfOSProcess'; > load. > > (Smalltalk at: #ConfigurationOfOSProcess) project bleedingEdge load. > > > Is the only issue updating to FileSystem, or are there other changes > that are needed for Pharo 2.0? > > > On Fri, Nov 9, 2012 at 9:35 AM, roberto.mine...@usi.ch > wrote: >> Hi, >> >> I'd like to script some shell commands in Pharo 2.0. >> Is there any way to do that in Pharo? It seems OSProcess class is suitable >> but seems it's not yet fully ported in Pharo 2.0. >> >> Thanks, >> Roberto >
Re: [Pharo-project] OSProcess in Pharo 2.0
I'm working on a simple library for NativeBoost that will execute commands on the shell and return stdin and stderr to the image. This will take me one or two weeks to complete though. Once I'm finished I'll post it on the list (I guess there's a lot of people who would want something like this). This library should (hopefully) make OSProcess obsolete. Cheers, Max On 09.11.2012, at 10:35, roberto.mine...@usi.ch wrote: > Hi, > > I'd like to script some shell commands in Pharo 2.0. > Is there any way to do that in Pharo? It seems OSProcess class is suitable > but seems it's not yet fully ported in Pharo 2.0. > > Thanks, > Roberto
Re: [Pharo-project] OSProcess in Pharo 2.0
oh. Better to follow: http://book.pharo-project.org/book/PharoTools/OSProcess/ This seems to work fine. I saw somewhere: "since os process isn't really reliable in Pharo-2.0". Is that/was that correct? On Tue, Nov 13, 2012 at 8:59 AM, Peter H. Meadows wrote: > Is OSProcess still the best/correct way? > > I've been using it in 2.0. Seems to work. > > load: > > MCHttpRepository > location: 'http://smalltalkhub.com/mc/dh83/fisleg/main' > user: '' > password: '' > > then do: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfOSProcess'; > load. > > (Smalltalk at: #ConfigurationOfOSProcess) project bleedingEdge load. > > > Is the only issue updating to FileSystem, or are there other changes > that are needed for Pharo 2.0? > > > On Fri, Nov 9, 2012 at 9:35 AM, roberto.mine...@usi.ch > wrote: >> Hi, >> >> I'd like to script some shell commands in Pharo 2.0. >> Is there any way to do that in Pharo? It seems OSProcess class is suitable >> but seems it's not yet fully ported in Pharo 2.0. >> >> Thanks, >> Roberto
Re: [Pharo-project] OSProcess in Pharo 2.0
On Tue, Nov 13, 2012 at 11:24 AM, Max Leske wrote: > I'm working on a simple library for NativeBoost that will execute commands on > the shell and return stdin and stderr to the image. > This will take me one or two weeks to complete though. Once I'm finished I'll > post it on the list (I guess there's a lot of people who would want something > like this). This library should (hopefully) make OSProcess obsolete. pleaeee -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
Re: [Pharo-project] OSProcess in Pharo 2.0
:D Thanks Damien On 15.11.2012, at 16:47, Damien Cassou wrote: > On Tue, Nov 13, 2012 at 11:24 AM, Max Leske wrote: >> I'm working on a simple library for NativeBoost that will execute commands >> on the shell and return stdin and stderr to the image. >> This will take me one or two weeks to complete though. Once I'm finished >> I'll post it on the list (I guess there's a lot of people who would want >> something like this). This library should (hopefully) make OSProcess >> obsolete. > > pleaeee > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >
Re: [Pharo-project] OSProcess in Pharo 2.0
On Thu, Nov 15, 2012 at 4:47 PM, Damien Cassou wrote: > On Tue, Nov 13, 2012 at 11:24 AM, Max Leske wrote: > > I'm working on a simple library for NativeBoost that will execute > commands on the shell and return stdin and stderr to the image. > > This will take me one or two weeks to complete though. Once I'm finished > I'll post it on the list (I guess there's a lot of people who would want > something like this). This library should (hopefully) make OSProcess > obsolete. > > pleaeee > > Don't be so rude with OSProcess please. This is a great tool and has been helping the community since a really long time. And Dave was always there willing to help as much as possible. > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > -- Mariano http://marianopeck.wordpress.com
Re: [Pharo-project] OSProcess in Pharo 2.0
On Nov 13, 2012, at 11:24 AM, Max Leske wrote: > I'm working on a simple library for NativeBoost that will execute commands on > the shell and return stdin and stderr to the image. > This will take me one or two weeks to complete though. Once I'm finished I'll > post it on the list (I guess there's a lot of people who would want something > like this). This library should (hopefully) make OSProcess obsolete. > > Cheers, > Max Excellent. I love to hear that. Now it will only replace OSProcess on system that support NB. Stef
Re: [Pharo-project] OSProcess in Pharo 2.0
On 16.11.2012, at 07:20, Stéphane Ducasse wrote: > > On Nov 13, 2012, at 11:24 AM, Max Leske wrote: > >> I'm working on a simple library for NativeBoost that will execute commands >> on the shell and return stdin and stderr to the image. >> This will take me one or two weeks to complete though. Once I'm finished >> I'll post it on the list (I guess there's a lot of people who would want >> something like this). This library should (hopefully) make OSProcess >> obsolete. >> >> Cheers, >> Max > > Excellent. I love to hear that. > Now it will only replace OSProcess on system that support NB. Yes of course. But NB will be everywhere soon, right? :-p > > Stef
Re: [Pharo-project] OSProcess in Pharo 2.0
On Nov 16, 2012, at 9:57 AM, Max Leske wrote: > > On 16.11.2012, at 07:20, Stéphane Ducasse wrote: > >> >> On Nov 13, 2012, at 11:24 AM, Max Leske wrote: >> >>> I'm working on a simple library for NativeBoost that will execute commands >>> on the shell and return stdin and stderr to the image. >>> This will take me one or two weeks to complete though. Once I'm finished >>> I'll post it on the list (I guess there's a lot of people who would want >>> something like this). This library should (hopefully) make OSProcess >>> obsolete. >>> >>> Cheers, >>> Max >> >> Excellent. I love to hear that. >> Now it will only replace OSProcess on system that support NB. > > Yes of course. But NB will be everywhere soon, right? :-p yep :) (but of course, "soon" is a subjective word... ) > >> >> Stef > >
Re: [Pharo-project] OSProcess in Pharo 2.0
On Nov 15, 2012, at 10:52 PM, Mariano Martinez Peck wrote: > > > On Thu, Nov 15, 2012 at 4:47 PM, Damien Cassou > wrote: > On Tue, Nov 13, 2012 at 11:24 AM, Max Leske wrote: > > I'm working on a simple library for NativeBoost that will execute commands > > on the shell and return stdin and stderr to the image. > > This will take me one or two weeks to complete though. Once I'm finished > > I'll post it on the list (I guess there's a lot of people who would want > > something like this). This library should (hopefully) make OSProcess > > obsolete. > > pleaeee > > > Don't be so rude with OSProcess please. This is a great tool and has been > helping the community since a really long time. And Dave was always there > willing to help as much as possible. Yes this is true. Dave is always supportive and I really appreciate his attitude. Ideally I would like to have both a nice one working everywhere. > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > > > > -- > Mariano > http://marianopeck.wordpress.com >
Re: [Pharo-project] OSProcess in Pharo 2.0
Hello 2012/11/16 Max Leske > > On 16.11.2012, at 07:20, Stéphane Ducasse > wrote: > > > > > On Nov 13, 2012, at 11:24 AM, Max Leske wrote: > > > >> I'm working on a simple library for NativeBoost that will execute > commands on the shell and return stdin and stderr to the image. > >> This will take me one or two weeks to complete though. Once I'm > finished I'll post it on the list (I guess there's a lot of people who > would want something like this). This library should (hopefully) make > OSProcess obsolete. > >> > >> Cheers, > >> Max > > > > Excellent. I love to hear that. > > Now it will only replace OSProcess on system that support NB. > > Yes of course. But NB will be everywhere soon, right? :-p > > What about mobile platforms? They not allow NB code generation approach (IOS for example). But I think OSProcess not work on such platforms too.
Re: [Pharo-project] OSProcess in Pharo 2.0
On 16.11.2012, at 11:42, Stéphane Ducasse wrote: > > On Nov 15, 2012, at 10:52 PM, Mariano Martinez Peck wrote: > >> >> >> On Thu, Nov 15, 2012 at 4:47 PM, Damien Cassou >> wrote: >> On Tue, Nov 13, 2012 at 11:24 AM, Max Leske wrote: >>> I'm working on a simple library for NativeBoost that will execute commands >>> on the shell and return stdin and stderr to the image. >>> This will take me one or two weeks to complete though. Once I'm finished >>> I'll post it on the list (I guess there's a lot of people who would want >>> something like this). This library should (hopefully) make OSProcess >>> obsolete. >> >> pleaeee >> >> >> Don't be so rude with OSProcess please. This is a great tool and has been >> helping the community since a really long time. And Dave was always there >> willing to help as much as possible. > > Yes this is true. Dave is always supportive and I really appreciate his > attitude. > Ideally I would like to have both a nice one working everywhere. > I didn't mean to step on anybody's toes. Sorry if I did. At the moment we would be completely and utterly lost without OSProcess. So yes, OSProcess is great. But then, for one, it's a VM plugin. There's also a lot of magic going on wich makes it kind of hard to debug sometimes. Talking of an "OSProcess replacement" was a bit harsh I reckon, what I actually ment was "OSProcess alternative", especially a light one (for now). Cheers, Max >> >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > >
Re: [Pharo-project] osprocess in pharo 2.0
good question. > For some reason I thought that OSProcess was integrated in Pharo 2.0, but it > appears that it is not in the image. Did I understand the issue incorrectly, > or was the class renamed to something else? we did not renamed the class > > If it is not in the image, was it already ported to SmalltalkHub? (I could > not find it) No because david did not move it. I could do it but I was waiting for him. > > I am asking because I would like to know if we should continue to load > OSProcess explicitly with Moose.
Re: [Pharo-project] osprocess in pharo 2.0
OSProcess was not ready for 2.0 when we closed the beta, so we did not include it. Now is working fine but since we are hours from release, is not good to have it there by default now (it will be for 3.0. then)... it would be really cool to have a metacello configuration in MetaRepoForPharo20, though. Esteban On Mar 6, 2013, at 6:38 PM, stephane ducasse wrote: > good question. > >> For some reason I thought that OSProcess was integrated in Pharo 2.0, but it >> appears that it is not in the image. Did I understand the issue incorrectly, >> or was the class renamed to something else? > > we did not renamed the class >> >> If it is not in the image, was it already ported to SmalltalkHub? (I could >> not find it) > > No because david did not move it. I could do it but I was waiting for him. >> >> I am asking because I would like to know if we should continue to load >> OSProcess explicitly with Moose. > >
Re: [Pharo-project] osprocess in pharo 2.0
Hi, Thanks for the answers. It's no problem that it is not in 2.0. I just wanted to make sure. It's already great that it works with 2.0. Cheers, Doru On Mar 6, 2013, at 7:43 PM, Esteban Lorenzano wrote: > OSProcess was not ready for 2.0 when we closed the beta, so we did not > include it. > Now is working fine but since we are hours from release, is not good to have > it there by default now (it will be for 3.0. then)... it would be really cool > to have a metacello configuration in MetaRepoForPharo20, though. > > Esteban > > On Mar 6, 2013, at 6:38 PM, stephane ducasse wrote: > >> good question. >> >>> For some reason I thought that OSProcess was integrated in Pharo 2.0, but >>> it appears that it is not in the image. Did I understand the issue >>> incorrectly, or was the class renamed to something else? >> >> we did not renamed the class >>> >>> If it is not in the image, was it already ported to SmalltalkHub? (I could >>> not find it) >> >> No because david did not move it. I could do it but I was waiting for him. >>> >>> I am asking because I would like to know if we should continue to load >>> OSProcess explicitly with Moose. >> >> > > -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one."
Re: [Pharo-project] osprocess in pharo 2.0
EstebanLM wrote > it would be really cool to have a metacello configuration in > MetaRepoForPharo20 There is one there :) - Cheers, Sean -- View this message in context: http://forum.world.st/osprocess-in-pharo-2-0-tp4674453p4675619.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Re: [Pharo-project] osprocess in pharo 2.0
On 2013-03-07, at 22:35, "Sean P. DeNigris" wrote: > EstebanLM wrote >> it would be really cool to have a metacello configuration in >> MetaRepoForPharo20 > > There is one there :) I wonder why it fails on the build-server? https://ci.inria.fr/pharo-contribution/job/OSProcess/
Re: [Pharo-project] osprocess in pharo 2.0
On Mar 8, 2013, at 3:49 AM, Camillo Bruni-3 [via Smalltalk] wrote: > I wonder why it fails on the build-server? It fails because ThisOSProcess class>>shutDown: includes "OSProcess accessor breakDependents", but OSProcess accessor returns nil because none of the platform packages are loaded by the 'Tests' group of ConfigurationOfOSProcess. You can load 'Tests' and 'All OS' via "--groups='All OS',Tests" with the slice for "Issue 7662: [ENH]: ConfigurationCommandLineHandler: Accept multiple group names" Going forward, I'm not sure whether Tests should depend on the OS packages. You may want to load just the current OS, for example. I think probably a good error message and maybe a retry to find a suitable OS class if the accessor is nil... cc: David Lewis - Cheers, Sean -- View this message in context: http://forum.world.st/osprocess-in-pharo-2-0-tp4674453p4675783.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Re: [Pharo-project] osprocess in pharo 2.0
thanks, I changed it and it sort of works: https://ci.inria.fr/pharo-contribution/job/OSProcess/ though an impressive number of 81 tests fail, that is almost 50% of all the tests. Is that normal? On 2013-03-08, at 17:13, "Sean P. DeNigris" wrote: > On Mar 8, 2013, at 3:49 AM, Camillo Bruni-3 [via Smalltalk] > wrote: >> I wonder why it fails on the build-server? > It fails because ThisOSProcess class>>shutDown: includes "OSProcess accessor > breakDependents", but OSProcess accessor returns nil because none of the > platform packages are loaded by the 'Tests' group of ConfigurationOfOSProcess. > > You can load 'Tests' and 'All OS' via "--groups='All OS',Tests" with the > slice for "Issue 7662: [ENH]: ConfigurationCommandLineHandler: Accept > multiple group names" > > Going forward, I'm not sure whether Tests should depend on the OS packages. > You may want to load just the current OS, for example. I think probably a > good error message and maybe a retry to find a suitable OS class if the > accessor is nil... > > cc: David Lewis > > > > > > - > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/osprocess-in-pharo-2-0-tp4674453p4675783.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Re: [Pharo-project] osprocess in pharo 2.0
On Fri, Mar 08, 2013 at 05:27:04PM +0100, Camillo Bruni wrote: > thanks, I changed it and it sort of works: > https://ci.inria.fr/pharo-contribution/job/OSProcess/ > though an impressive number of 81 tests fail, that is almost 50% of all the > tests. > Is that normal? > I wouldn't call in "normal", but the full test suite requires an interpreter VM on Unix. To check for failures associated with the image, as opposed to VM features, I need to run the tests on an interpreter VM. Unfortunately I cannot open a Pharo image on an interpreter VM any more, possibly due to something failing in the startUp sequence. If anyone can explain what has changed I'd appreciate the help, because I have not been able to figure it out. Dave
Re: [Pharo-project] osprocess in pharo 2.0
On Fri, Mar 08, 2013 at 08:13:19AM -0800, Sean P. DeNigris wrote: > On Mar 8, 2013, at 3:49 AM, Camillo Bruni-3 [via Smalltalk] > wrote: > > I wonder why it fails on the build-server? > It fails because ThisOSProcess class>>shutDown: includes "OSProcess accessor > breakDependents", but OSProcess accessor returns nil because none of the > platform packages are loaded by the 'Tests' group of ConfigurationOfOSProcess. > Thanks Sean, So I should add a nil check in the shutDown: method, right? I'll do it later tonight when I get home. Dave
Re: [Pharo-project] osprocess in pharo 2.0
On Fri, Mar 08, 2013 at 11:58:38AM -0500, David T. Lewis wrote: > On Fri, Mar 08, 2013 at 08:13:19AM -0800, Sean P. DeNigris wrote: > > On Mar 8, 2013, at 3:49 AM, Camillo Bruni-3 [via Smalltalk] > > wrote: > > > I wonder why it fails on the build-server? > > It fails because ThisOSProcess class>>shutDown: includes "OSProcess > > accessor breakDependents", but OSProcess accessor returns nil because none > > of the platform packages are loaded by the 'Tests' group of > > ConfigurationOfOSProcess. > > > > Thanks Sean, > > So I should add a nil check in the shutDown: method, right? I'll do it later > tonight when I get home. Fixed in OSProcess-Base-dtl.31 Dave
Re: [Pharo-project] osprocess in pharo 2.0
David T. Lewis wrote > So I should add a nil check in the shutDown: method, right? Would it be a good idea to do a lazy initialization in #accessor? For example, if I load Base, and then I separately add the OS packages, I think I would have to manually reinitialize OSP before they will be picked up... - Cheers, Sean -- View this message in context: http://forum.world.st/osprocess-in-pharo-2-0-tp4674453p4675867.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Re: [Pharo-project] osprocess in pharo 2.0
On Fri, Mar 08, 2013 at 05:25:55PM -0800, Sean P. DeNigris wrote: > David T. Lewis wrote > > So I should add a nil check in the shutDown: method, right? > > Would it be a good idea to do a lazy initialization in #accessor? For > example, if I load Base, and then I separately add the OS packages, I think > I would have to manually reinitialize OSP before they will be picked up... > ThisOSProcess>>processAccessor already is lazy initialized. I think that this particular issue was probably caused by doing a shutDown: with no processor accessor, which I think might happen if the image was running on e.g. RISC OS. So I fixed the shutDown: so it will not fail in a case like that. If someone was running the unit tests for OSProcess and did not have the platform package(s) loaded, then the tests will fail. That is a test configuration issue. Dave
