On Fri, Feb 20, 2004 at 03:25:44PM -0700, Ian D. wrote:
So do you recommend that I don't use it at all? If it appears to
be working for me, then is it safe? Are these "specific compiles"
always broken, or just sometimes broken (unpredictably)?
I don't know the answer. I'm not well enough trained in reading
the source code to know for sure. I use a private version that
has been fixed. Bart Schaefer offered his for general use
as well.
As for variable scoping, try this. I get "MYVAR is foo". Notice the
"Forking" line. I think any variables set by a child won't be seen
by the parent, if typical UNIX fork() mechanisms are used.
Yes, you are correct, as Bart also pointed out just now. I hadn't
paid close enough attention to your original contextual statements.
Sorry about that.
--------------- start ---------------
VERBOSE=on
MYVAR="foo"
:0c
{
MYVAR="bar"
:0
/dev/null
}
LOG="
MYVAR is $MYVAR
"
:0
/dev/null
--------------- end ---------------
Yes, the fork won't see the assignment, true enough.
Dallman
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail