Werner LEMBERG <[email protected]>:
>
> > Actually, now that I think about it, the right semantics for
> > ".hygiene" is probably "hide everything *currently defined* that
> > hasn't been declared visible". That way you can define macros after
> > a .hygiene call and they'll be visible unless you do another
> > .hygiene call.
>
> What about doing the autoconf approach with regular patterns to allow
> and disallow function names?
Possible, but smells of overengineering to me.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
