Re: Issues with exported functions

[Chet Ramey]

On 9/28/14, 12:31 PM, Ángel González wrote:

> There's also the middleground of not parsing the environment variables
> before they are going to be used. That avoids the issues caused by
> parsing what is not needed *and* doesn't break backwards compatibility.
> See the patch I sent a couple days ago.

That's a reasonably elegant extension, but it doesn't really solve the
problem any better than fixing the underlying parser problem.  A user who
can figure out how to pass a function with the appropriate name encoding,
which at this point nobody has figured out to do remotely, can more than
likely arrange for that function to be called, at which point it will be
parsed and any underlying parser bug exposed.

Chet

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