LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Frank Mittelbach <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Mon, 20 Jan 2003 20:16:39 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Lars Hellström writes:

 > Would it break anything if the LaTeX core would say
 >
 >   \ifx \protected\@undefined \def\protected{} \fi
 >
 > and \protected was used before each definition of a LICR command?

probably not (well, probably yes :-) i have yet to see a single change that
doesn't break something, but for most purposes that should be a clear no).

However, that would be fairly in efficient way to use the eTeX feature, ie if
eTeX would be unconditionally used one could run far more efficient code since
a lot of that \ifx\protect\typeset@protect could go away (and an LICR command
on top-level expansion could be reduced to just two tokens)

however, as a compatible start that actually works with TeX one could simply
go

 \ifx \protected\@undefined \def\protected{}
 \else
   \WARNING-This-may-loose-characters-if-you-are-not-careful-better-use-etex
 \fi
 \protected\def\@current@cmd@math....

and that should do the trick

frank

ATOM RSS1 RSS2