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
Condense Mail Headers

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

Print Reply
Mime-Version:
1.0 (Apple Message framework v930.3)
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
From:
Will Robertson <[log in to unmask]>
Date:
Wed, 18 Feb 2009 11:23:46 +1030
In-Reply-To:
Content-Type:
multipart/signed; boundary=Apple-Mail-14-1060672142; micalg=sha1; protocol="application/pkcs7-signature"
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments:
text/plain (956 bytes) , smime.p7s (2446 bytes)
On 18/02/2009, at 10:42 AM, Manuel Pégourié-Gonnard wrote:

> Will Robertson a écrit :
>> So here, while \the isn't a macro, it will expand when used  
>> correctly in
>> an edef (e.g., \edef\foo{\the\baselineskip} ).  I've explicitly  
>> caught
>> undefined macros to return "F" because it just seemed more logical  
>> that
>> way.
>>
> In my understanding of the term, macros are always "expandable". I  
> think
> in the context of this function, "expandable" should mean the same  
> as in
> the TeXbook, (p. 212-214 in my edition) after the text

Ah, okay. Foolishly, I don't have a copy handy.
That naming makes more sense now.

>> Now let's consider the control sequences that are expanded whenever
>> expansion has not been inhibited. Such control sequences fall into
>> several classes:
>
> Here macros are described as "expandable" regardless of whether they  
> are
> defined or not.

Odd. I suppose it's understandable, though.

Thanks for the help,
Will



ATOM RSS1 RSS2