Re: Re: Run option
- To: mathgroup at smc.vnet.net
- Subject: [mg71975] Re: [mg71946] Re: Run option
- From: "Chris Chiasson" <chris at chiasson.name>
- Date: Wed, 6 Dec 2006 06:04:08 -0500 (EST)
- References: <firstname.lastname@example.org> <200612051104.GAA27231@smc.vnet.net>
I knew someone was going to mention ReadList. I need the exit status
codes so I can detect failure. I also need to support paths with
spaces in both the command and in the arguments on the Windows
platform. This involves a special trick detailed here:
WRI really should not rely on ReadList - there should simply be an
option to Run.
Thanks for the suggestion. It will probably make me look at bending
ReadList to my will a little harder.
On 12/5/06, John Jowett <John.Jowett at cern.ch> wrote:
> It is often better to use ReadList than Run. I always use this for
> running external "console" programs. No command window appears and it also
> has the advantage that you can easily capture and manipulate the program's
> output stream.
> Note that you need to prefix the command string with "!". You can also
> use Import which gives more ways of dealing with the output.
> I have often wondered if there is any disadvantage to this (why is it not
> documented?) but have not found any.
> John Jowett
> "Chris Chiasson" <chris at chiasson.name> wrote in message
> news:el11sv$44a$1 at smc.vnet.net...
> Hi, please add an option to Run that can disable the command window
> that pops up when an external command is run (on Windows platforms).
> The present behavior becomes quite annoying when multiple commands are
> run successively in a batch job.
Prev by Date:
Re: Points sampled by N[Derivative]
Next by Date:
Re: Solving General Linear Equations
Previous by thread:
Re: Run option
Next by thread:
RE: Re: Run option