[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    ash builtin function `read' called without arguments...
From:       Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn () axis ! com>
Date:       2019-01-30 13:01:30
Message-ID: nycvar.QRO.7.76.1901301339540.3302 () enwn ! fr ! nkvf ! pbz
[Download RAW message or body]

...sets implicit variable REPLY, even though ASH_BASH_COMPAT is not 
set.

That was introduced in 2010-01-12 with commit 
045f4ad92c07434625e168bc8c37aa0e89f6e58e.  The comment is still 
present in the code:

+               /* $IFS splitting. NOT done if we run "read"
+                * without variable names (bash compat).
+                * Thus, "read" and "read REPLY" are not the same.
+                */

Still, this is a bashism and should be tested with IF_ASH_BASH_COMPAT.

Dash does not support that:

$ read
dash: 1: read: arg count

and The Open Group Base Specifications Issue 6 does not document that 
behaviour.

Yes, I suspect the "feature" may be already abused.

What do you think?


Cheers,

-- 
Cristian
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]