On Sunday 19 July 2009 01:35:22 Garrett Cooper wrote: > On Sat, Jul 18, 2009 at 10:26 PM, Mike Frysinger<[email protected]> wrote: > > On Sunday 19 July 2009 01:15:04 Garrett Cooper wrote: > >> /bin/sh should remain the standard, but a number of changes need > >> to happen to the .sh scripts to make them POSIX compatible, e.g. > >> backticks execution should become $(), etc. Let's not make things > >> bash-only... > > > > umm, `cmd` is in POSIX > > Not anymore; a fellow bourne shell-ist at work noted that it > wasn't POSIX compliant anymore, after consulting the POSIX 2001 > reference: > > http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/com.ibm.a >ix.baseadmn/doc/baseadmndita/korn_shell_comm_sub.htm
what ibm has to say on the topic is irrelevant, as does *ksh* documentation, as does outdated POSIX specs (2001 here). what is relevant is POSIX itself: http://www.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03 $(...) is preferred style wise due to nesting capabilities, but that doesnt mean it isnt in the standard. i still prefer `...` in make scripts because it avoids having to do $$(...) to escape it for make. -mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge
_______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
