#13157: inline_fortran is STILL broken on OS X
----------------------------------+-----------------------------------------
Reporter: benjaminfjones | Owner: was
Type: defect | Status: needs_review
Priority: major | Milestone: sage-5.3
Component: interfaces | Resolution:
Keywords: fortran osx | Work issues:
Report Upstream: N/A | Reviewers: Karl-Dieter Crisman
Authors: Jeroen Demeyer | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by jdemeyer):
I tested this on many platforms and it works. Is that sufficient for
positive review then?
Replying to [comment:8 kcrisman]:
> Any reason for the change of standard error to standard output instead
of the previous vice versa? It does seem more natural given the names of
the terms, but I'm not a bash expert...
The redirection
{{{
1>&2 >foo
}}}
is equivalent to
{{{
>foo
}}}
It's like saying: redirect stdout to stderr. Oh, never mind, redirect it
to `foo` instead. This doesn't really make sense, so I assume it's a
mistake.
While
{{{
>foo 2>&1
}}}
means: redirect stdout to `foo`. Now redirect stderr to the '''new'''
stdout, which is `foo`. This therefore redirects both stdout and stderr
to `foo`.
''Off topic and just for educational value'': the redirection
{{{
2>&1 >foo
}}}
would mean: redirect stderr to the '''current''' stdout. Now redirect
stdout (but not stderr) to `foo`.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13157#comment:9>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
