On Thu, Nov 05, 2009 at 10:36:31PM -0500, Schwab,Wilhelm K wrote:
Dave,
First, many thanks for the packages! All I am aware that I did was comment out the line in #initialize that opens the workspace and re-save. Can you make that change and post a new version? If for any reason that turns out not to load cleanly for me, then I can track down what else I might have done and makge that available.
I'll take a look at it again this weekend, and update if I can find the underlying problem. I think there is some difference in Pharo that is making the pipe processing work incorrectly (hence the error in #initialize but there are issues elsewhere too, see the unit tests). I have not figured it out yet, so if anyone has any ideas please let me know. Dave
Having command shell come along with the pipes is not a very big problem. Having the packages load cleanly would be huge in itself.
I hope to use pipes to control gnuplot from Pharo. Another possible use would be to create a LaTeX IDE, but that is farther away and harder to justify. Why write one at all? TeX maker is pretty good, but it would be nice to embed Smalltalk expressions that can generate LaTeX source; I did that in Dolphin and it worked reasonably well. One weakness of TeX maker (perhaps more a weakness of TeX Live, or maybe I just haven't found it yet) is a tool such as texify that does everything needed to update a document.
Bill
-----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of David T. Lewis Sent: Thursday, November 05, 2009 4:00 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Error handling failure during load
On Thu, Nov 05, 2009 at 02:22:48PM -0500, Schwab,Wilhelm K wrote:
Stef,
The classes in CommandShell-Piping would be better separated from CommandShell. That said, I do not terribly much care about loading CommandShell to get pipes - I care a lot that it won't load w/o proceeding past two warnings followed by a debug/edit/proceed cycle. I have no idea whether it is a true fix or not, but I commented out the offending line and re-saved the package, only to find that it loads w/o hassles. If it really is that simple, the repository should be fixed.
Bill,
Please send me your patch for this (lewis at mail dot msen dot com).
r.e. CommandShell-Piping FYI when I split OSProcess into two packages (OSProcess and CommandShell) many years back, I split it in such a way that there were no dependencies between the two, and that put the piping support in CommandShell (which of course is where piping is needed). Back then I don't think anybody really used either package, so it did not matter where I did the split ;-) Now it seems that folks have found uses for the piping stuff, and I guess it would be better moved into OSProcess or maybe a separate package. It's a bit of work to do that and breaks backward compatibility of the packages, so I have not done anything to change it.
Thanks, Dave