On 8/10/21 12:39 PM, Robert Elz wrote:

   | In this case, you are using features outside what POSIX specifies.

Using a variable name that's outside what POSIX specifies is hardly
using a feature that's outside POSIX - if it were then there would be
no safe non-trivial scripts, since any variable name might be made magic
by some shell or other (and no, there's nothing special about all upper
case variable names).    Only those defined by POSIX to have some special
meaning mean something, and even those can be re-used for another purpose
as long as one doesn't expect the special behaviour to function correctly.

As long as POSIX doesn't define a variable to have some special meaning, it
doesn't have anything to say about how a shell chooses to use it. It's not
a POSIX issue, period.

In this case, as is the case with just about all of the bash special
variables, you can unset it and it will lose its special meaning.

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    c...@case.edu    http://tiswww.cwru.edu/~chet/

  • GROUPS Franklin, Jason
    • Re: G... Greg Wooledge
      • R... Franklin, Jason
        • ... Greg Wooledge
        • ... Chet Ramey
        • ... Robert Elz
          • ... Štěpán Němec
            • ... Andreas Schwab
          • ... Chet Ramey
          • ... Robert Elz
            • ... Chet Ramey
            • ... Robert Elz
    • Re: G... Chet Ramey
    • Re: G... Franklin, Jason
      • R... Dmitry Goncharov via Bug reports for the GNU Bourne Again SHell
      • R... Chet Ramey
    • Re: G... Franklin, Jason
      • R... Greg Wooledge
        • ... Franklin, Jason

Reply via email to