On Tue, Sep 10, 2002 at 10:59:15AM -0700, Bruce Korb wrote:
> Another approach is to go ahead and emit the Makefile.in,
> but also emit a warning like this:
>
> cat >&2 <<_EOF_
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>
> WARNING: you seem to be misusing ${variable} in ${filename}
>
> ${variable} is always used by automake, but it appears in
> conditional text. This is almost certainly a mistake.
> See: http://sources.redhat.com/ml/automake/2002-06/msg00143.html
> And see: http://www.gnu.org/software/automake/unconditional-use.html
> for more information.
>
> MEANWHILE: we are creating the output file so you won't be
> dead in the water, but you should fix your ${filename} file
> and be aware there may be unexpected results.
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> _EOF_
Gaaaa!
A simple warning message, please:
${filename}: WARNING: ${variable} appears in conditional text
The rest belongs in the manual, *not* on stderr.
>
> sleep 30
>
*Shudder*
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. [EMAIL PROTECTED]
| | /
[...] despite reports to the contrary, it is the rare programmer who
permanently loses his sanity while coding ("permanently" being the
operative word).
- Eric E. Allen
