Re: iocshCmd, redirection, and function pointers

["Ernest L. Williams Jr." <ernesto@slac.stanford.edu>]

Hi everyone,

Looks like I have a work-around for what was happening under RTEMS while 
using iocshCmd:
Thanks to Till:  )


# This one does not work: as reported by Stephanie Allison in this 
tech-talk thread
#iocshCmd("dbior > /data/iocInfo/IOC.dbior")

# However, this one does work under RTEMS. Thanks to Till:
Cexp@ioc-b34-ev02> > "/data/iocInfo/IOC.dbior" : dbior()



Cheers,
Ernest



On 03/14/2012 05:14 PM, Kim, Kukhee wrote:
> Hi Eric;
>
> The epicsStdioRedirect.h itself already includes the epicsStdio.h file.
> Probably, we should merge those two files to one file.
>
> Thank you.
> Best regards,
> Kukhee
> --------------------------------------------
> Kukhee Kim
> SLAC National Accelerator Laboratory
> 2575 Sand Hill Rd, MS 64
> Menlo Park, CA 94025
> Email: khkim@SLAC.Stanford.EDU
> Phone: (650)926-4912
>
>
> -----Original Message-----
> From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Eric Norum
> Sent: Wednesday, March 14, 2012 8:39 AM
> To: EPICS Tech Talk
> Subject: Re: iocshCmd, redirection, and function pointers
>
> On Mar 14, 2012, at 3:12 AM, Dirk Zimoch wrote:
>
> > Eric Norum wrote:
> > > For I/O redirection to work a source file must include epicsStdioRedirect.h.
> > This sucks.
> Perhaps, but it does work across all supported platforms.
>
> > It this is the case, I would say that there is something wrong with the EPICS redirection. Code should not need to know about its "environment". This contradicts any good programming practice.
> When this was originally implemented we felt it should be optional.  Perhaps now after 10 years in the field we should just add
> #include<epicsStdioRedirect.h>
> in epicsStdio.h.