Received: by nummer-3.proteosys id <01C19442.D4DDFE8C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:38:50 +0100 In-Reply-To: Your message of "Wed, 10 Oct 90 12:12:55 +0700." <9010101804.AA23890@s46.csrd.uiuc.edu> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19442.D4DDFE8C" x-vm-v5-data: ([nil nil nil nil nil nil nil t nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Re: VERB IN HEADINGS (full) Date: Sun, 21 Oct 1990 17:30:40 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 243 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19442.D4DDFE8C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The idea of using \meaning was too good to be true. In the next TUGboat there will be an article by Ron Whitney that uses this trick. When I read a draft of that article I thought 'Cute. Let's try using it'. Here's what's wrong with using it for verbatim text: \def\verb#1{\def\text{#1}\meaning\text} \verb{1&2} \verb{1#3} which gives \verb #1->\def \text {#1}\meaning \text #1<-1##3 ! Illegal parameter number in definition of \text. 3 \verb #1->\def \text {#1 }\meaning \text Ron also suggested scooping up the text as a token list, writing that out and reading it in (his context was a bit different, but that's irrelevant for now). Here's what's wrong with that: \def\verb#1{\toks0=3D{#1}\showthe\toks0 } \verb{1#3} gives \verb #1->\toks 0=3D{#1}\showthe \toks 0 #1<-1##3 That is, the parameter character gets duplicated. It seems like implementing verbatim will have to be done the hard way. Or at least *some* hard way. Or a lot of exceptions will have to be made. Victor Eijkhout phone: +1 217 244-0047 Center for Supercomputing Research and Development University of Illinois at Urbana-Champaign 305 Talbot laboratory 104 South Wright street Urbana, Illinois 61801-2932, USA home: 2503 W. Springfield Av, Apt. K-4, Champaign 61821, USA ------_=_NextPart_001_01C19442.D4DDFE8C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: VERB IN HEADINGS (full)

The idea of using \meaning was too good to be = true.

In the next TUGboat there will be an article by Ron = Whitney
that uses this trick. When I read a draft of that = article
I thought 'Cute. Let's try using it'. Here's what's = wrong with
using it for verbatim text:

\def\verb#1{\def\text{#1}\meaning\text}
\verb{1&2}
\verb{1#3}

which gives

\verb #1->\def \text {#1}\meaning \text
#1<-1##3
! Illegal parameter number in definition of = \text.
<to be read again>
          &nbs= p;        3
\verb #1->\def \text {#1
          &nbs= p;            = ; }\meaning \text

Ron also suggested scooping up the text as a token = list, writing
that out and reading it in (his context was a bit = different,
but that's irrelevant for now). Here's what's wrong = with that:

\def\verb#1{\toks0=3D{#1}\showthe\toks0 }
\verb{1#3}

gives

\verb #1->\toks 0=3D{#1}\showthe \toks 0
#1<-1##3

That is, the parameter character gets = duplicated.
It seems like implementing verbatim will have to be = done
the hard way. Or at least *some* hard way.

Or a lot of exceptions will have to be made.

Victor = Eijkhout           = ;          phone: +1 217 = 244-0047
 Center for Supercomputing Research and = Development
 University of Illinois at = Urbana-Champaign
 305 Talbot laboratory
 104 South Wright street
 Urbana, Illinois 61801-2932, USA

home: 2503 W. Springfield Av, Apt. K-4, Champaign = 61821, USA



------_=_NextPart_001_01C19442.D4DDFE8C--