[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Groff] Hygienic mode design

From: Werner LEMBERG
Subject: Re: [Groff] Hygienic mode design
Date: Wed, 05 Mar 2014 07:27:13 +0100 (CET)

> 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?  Example from `pkg.m4':


In autoconf, the patterns get collected in a log file during a call to
the m4 preprocessor, and later on the perl script `autom4te' scans all
user-defined macros against those patterns, aborting if there is a
match with a forbidden pattern.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]