On Mon, 2008-02-11 at 12:59, Guillem Jover wrote:
On Mon, 2008-02-11 at 11:46:49 -0000, Adam D. Barratt wrote:
[...]
I've now implemented a check for >& or <& followed by anything other
than - or a string of digits. I've left the check for bare &> in
place, as that's a bashism regardless of the surrounding context.
For the case of expansion, I suppose it should be enough to ignore the
cases there's a variable, like in:
$ a=2
$ echo foo >&$a
as to handle that properly, would imply parsing most of the shell
script.
Cases involving a variable will currently get flagged as potential issues.
I'm debating whether to leave it like that, on the assumption that most such
uses will involve the variable being a filename rather than a file
descriptor.
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
