[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: serious flaw of @c
From: |
Werner LEMBERG |
Subject: |
Re: serious flaw of @c |
Date: |
Sat, 22 Nov 2008 01:13:03 +0100 (CET) |
> I don't know any way to make a comment character in texinfo.tex,
> i.e., a way to say \let\foo=%. Do you?
Hmm, I've never thought about that. And since comment removal works
before macro expansion (at least I think so), I believe it's
impossible.
> There are no characters available to make be catcode 14, as far as
> I've ever been able to think of.
In my CJK package, I use character code 0x7F for various purposes
since this is not used anywhere else, in no encoding. So adding
\catcode "7F=14
somewhere in texinfo.tex would make this character available as a
comment character for all encodings (save EBCDIC) -- without *any*
problems. What do you think?
> Lilypond and/or groff are continually stretching Texinfo to its
> utter limits and I think you have just surpassed them.
Hehe.
> Forgetting about the current @macro stupidity, can you think of a
> different design for macros altogether that would be alleviate these
> issues?
Do you mean a different design of handling the current @macro syntax,
or a complete new way of designing macros?
Werner
- serious flaw of @c, Werner LEMBERG, 2008/11/21
- Re: serious flaw of @c, Karl Berry, 2008/11/21
- Re: serious flaw of @c,
Werner LEMBERG <=
- Re: serious flaw of @c, Karl Berry, 2008/11/21
- Re: serious flaw of @c, Werner LEMBERG, 2008/11/22
- Re: serious flaw of @c, Karl Berry, 2008/11/23
- Re: serious flaw of @c, Patrice Dumas, 2008/11/25
- Re: serious flaw of @c, Werner LEMBERG, 2008/11/25
- Re: serious flaw of @c, Werner LEMBERG, 2008/11/22
- Re: serious flaw of @c, Karl Berry, 2008/11/23