#7632: Add to developer's guide information how to write portable code.
------------------------+---------------------------------------------------
Reporter: drkirkby | Owner: drkirkby
Type: defect | Status: new
Priority: major | Milestone: sage-4.3
Component: porting | Keywords:
Work_issues: | Author:
Upstream: N/A | Reviewer:
Merged: |
------------------------+---------------------------------------------------
As discussed on sage-devel, we need to document how to write portable
POSIX conforming code, using best-practices. One such example, which
started the discussion, was using
{{{
test "$1" && test "$2"
}}}
and NOT
{{{
test "$1" -a "$2"
}}}
It would be wise to cite the URL for the 2004 POSIX standard (IEEE Std
1003.1, 2004 Edition), in the developers guide. The URL is:
http://www.opengroup.org/onlinepubs/009695399/
(There is a later 2008 POSIX standard, but some of changes in this may not
be implemented in everyone's operating system, whereas most operating
systems will implement the 2004 standard).
Unfortunately, due to what I believe is probably the use of frames, all
URLs on this site appear to be the same. As such, if directing people to a
URL, right-click on the item required, and copy the URL. E.g for the
'test' tool, it is:
http://www.opengroup.org/onlinepubs/009695399/utilities/test.html
For 'cp' it is
http://www.opengroup.org/onlinepubs/009695399/utilities/cp.html
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7632>
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.
