LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Proportional 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:
Hans Aberg <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Mon, 20 Oct 1997 17:02:16 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
  Should not \@ifdefinable be changed so that it does not check
\@ifundefined? This will make the implementation of different defining
command simpler and clearer. (As I would rather not get into the LaTeX
trickery of temporarily canceling \@ifundefined in \@ifdefinable, I would
prefer making my own version of \@ifdefinable which do not check
\@ifundefined.)

  I get the following variations; all should check \@ifdefinable without
\@ifundefined, but differ in the other respects:
    define
    new         If undefined, then define, else error.
    renew       If defined, then define, else error.
    provide     If undefined, then define, else do nothing.
    override    If define, then define, else do nothing.

(I do not want to go much into the context, but the problem shows up when
trying to do new variations of \newcommand, \newenvironment, \newobject,
etc.)

  Hans Aberg
                  * Email: Hans Aberg <mailto:[log in to unmask]>
                  * AMS member listing: <http://www.ams.org/cml/>

ATOM RSS1 RSS2