Tony Mechelynck wrote: > As for "erroneously" -- I agree with Bram that #!sh is supposed to mean > the original Bourne shell, not Bourne-again, not Korn, and quite > possibly before POSIX was invented. Anything which the original Bourne > shell did not support should not be used in a script starting #!sh (or > #!/bin/sh etc.) or else someday you'll feed one of these scripts to a > surviving copy of the original Bourne (not-again) shell and be surprised > that it doesn't work.
While forwards compatibility is nice it's not usually the case. Are you suggesting that #!/usr/bin/python #!/usr/bin/perl etc. scripts should only be written to the first released version of those languages? The fact is that #!/bin/sh scripts are run by a POSIX sh interpreter on the vast majority of systems. That dictates what the default should be IMHO. cheers, Pádraig. p.s. why is "print" highlighted as a keyword in sh scripts. grrr. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
