[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rt-devel
Subject:    Re: [Rt-devel] output on stderr and not using return values
From:       Jesse Vincent <jesse () bestpractical ! com>
Date:       2007-12-26 21:22:03
Message-ID: 20071226212203.GO22917 () bestpractical ! com
[Download RAW message or body]




On Fri, Dec 21, 2007 at 05:47:10PM +0100, Camenzind Patrick (KSDB 533) wrote:
> I just started using the RT(v3.6.3) command line interface for scripting
> purposes and was wondering why it doesn't make use of return values at
> all, means wether a command was successfully done or not can only be
> recognized by comparing the output strings on /dev/stderr as it always
> returns zero as returnvalue... this leads me directly to my second
> question: why not using /dev/stdout for outputs instead? It took me
> about one day to figure out why my string comparison didn't work :-( 

I'd love a patch to offer sane return values.  As to why we're using
STDERR rather than STDOUT,  the best I can offer is to plead "historical
insanity"

Best,
Jesse


> 
> any ideas?
> 
> 
> Regards
> 
> Patrick
> _______________________________________________
> List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
> 
> SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
> 
> If you sign up for a new RT support contract before December 31, we'll take
> up to 20 percent off the price. This sale won't last long, so get in touch today.
>     Email us at sales@bestpractical.com or call us at +1 617 812 0745.
> 

-- 
_______________________________________________
List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:

If you sign up for a new RT support contract before December 31, we'll take
up to 20 percent off the price. This sale won't last long, so get in touch today. 
    Email us at sales@bestpractical.com or call us at +1 617 812 0745.
[prev in list] [next in list] [prev in thread] [next in thread]