> This patch replaces a couple of 255s with (N(yytext)-1), which keeps up
> with changes in the size of yytext. As a bonus it communicates with me
> what the significance of the value to me. The macro recogniser could
> still be improved (take 1 character and look for multiple character if
> the catcode, aka lexcode, is the right thing). I think the right thing is
> letter, but check the nearest copy of the TeXbook. Once that has
> happenned the spaces can be icorporated into the main hash table.
I think copying the behaviour of TeX itself is the best thing to do when
parsing .tex. I have not looked at math_parser.C too hard yet, but I
don't think it is as TeXish as it might be... IIRC the TeXBook gives a
pretty detailed insight in the parsing process.
> If yytext changes into wide charcaters then the use of N macro will mean
> the patch will continue to do the right thing. The N macro is declared in
> several X11 headers, I think.
Excuse my ignorance: how does TeX handle wide charcters?
> P.S. If you I going to ive you new math_hash.C, do you want ANSI C or a
> C++ class? If the latter what do you want in called?
Maybe I should work on my English parser as well... Please?
I think, C++ should be preferable within LyX in most cases. And I don't see
a compelling reason why something as complex as a TeX parser should be done
in C.
Andre', off to find that matrix problem...
--
André Pönitz ........................................ [EMAIL PROTECTED]
