[Swift-devel] New built-in system, request for comments

Ketan Maheshwari ketan at mcs.anl.gov
Mon Apr 7 12:45:52 CDT 2014


Thanks, that makes sense. On a related note, currently, Swift sends version
and runid to stdout and progress log to stderr, I think it would be better
if everything Swift produces go to stderr and only user specified output go
to stdout.


On Sat, Apr 5, 2014 at 8:47 PM, Hategan-Marandiuc, Philip M. <
hategan at mcs.anl.gov> wrote:

> On Sat, 2014-04-05 at 19:59 -0500, Ketan Maheshwari wrote:
> > I agree this might not be needed in most cases. I was thinking of
> commands
> > or external programs that emit both stdout and stderr and say the list of
> > files that needs to be mapped are emitted only on one of the streams, in
> > such case user might want to ignore the other stream. Exitcode in this
> > context is a different issue.
> >
> > For instance, user might have a Swift script that produce user written
> > trace() on stdout while progress log on stderr. In such case, this might
> be
> > useful:
> >
> > file folder[ ] < array_mapper; files = system ("swift genfiles.swift",
> 1) >;
>
> If we're trying to simulate shell commands, why re-invent the wheel and
> not use system("swift genfiles.swift 2>/dev/null")?
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20140407/9fcd049b/attachment.html>


More information about the Swift-devel mailing list