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