l...@gnu.org (Ludovic Courtès) writes:
> Honestly, I wouldn’t worry about the propagation of $GUILE_LOAD_PATH &
> co. to subprocesses, because we know there’s none anyway.
That policy will lead to future where libguile-using programs break in
random ways when they happen to be subprocesses of each other.
Shouldn't we be setting a better example than that?
If we assume that Guile will never be widely used, and encourage usage
patterns that will cause things to break if it ever becomes more
successful, then we are pretty much guaranteeing a bleak future for
Guile.
Isn't correctness more important than brevity?
What do you think?
Mark
