On Tuesday 18 December 2012 11:21:45 Mark Miesfeld wrote:
> On Tue, Dec 18, 2012 at 8:50 AM, Leslie Turriff
>
> <jlturr...@centurytel.net> wrote:
> > In bash scripts it is common to see stderr redirected to stdout
> > with 2>&1 so that they can be written to a common file. I see a few
> > references to redirection in the Language Reference, but none of them
> > address this issue. Is there an analogue to this paradigm in ooRexx?
>
> What / where do you want this to happen? I.e. in a command you're
> sending to the shell?
>
Sorry; thinking about this more, I think that it is a non-issue. A
bash
script that I'm converting has a lot of
echo "some text" 2>&1
statements in it. I'm not sure that there is any purpose to having the
redirections in those statements, and I can probably ignore that.
>
> An analogue within Rexx code, in ooRexx, might be to use the .Monitor
> objects. Although I haven't fooled with that for a long time.
>
> >From rexxref.pdf
>
> 6.4. The Error Monitor (.ERROR)
> This monitor object (see The Monitor Class) holds the error stream
> object. You can redirect the trace
> output in the same way as with the output object in the Monitor class
> example. The default for this object’s initial destination is the .STDERR
> stream.
>
> If you play around with that, you might get what you want.
>
Thanks, Mark.
Leslie
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
