X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil]
	["424" "Thu" "25" "June" "1998" "12:53:00" "+1000" "Richard Walker" "Richard.Walker@CS.ANU.EDU.AU" nil "9" "Re: Modules" "^Date:" nil nil "6" nil nil nil nil nil]
	nil)
Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1])
	by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id EAA08990;
	Thu, 25 Jun 1998 04:53:26 +0200 (MET DST)
Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <1.A5CD4EF8@listserv.gmd.de>; Thu, 25 Jun 1998 4:53:24 +0200
Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE
          (LISTSERV-TCP/IP release 1.8b) with spool id 370395 for
          LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 25 Jun 1998 04:53:13 +0200
Received: from ricetub.anu.edu.au (richard@ricetub.anu.edu.au [150.203.166.61])
          by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id EAA04770
          for <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>; Thu, 25 Jun 1998 04:53:06
          +0200 (MET DST)
Received: (from richard@localhost) by ricetub.anu.edu.au (8.8.2/8.8.2) id
          MAA13499; Thu, 25 Jun 1998 12:53:00 +1000 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <980624151914.48d9@vms.rhbnc.ac.uk>
X-Mailer: VM 6.29 under Emacs 19.34.1
Message-ID:  <199806250253.MAA13499@ricetub.anu.edu.au>
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
In-Reply-To:  <980624151914.48d9@vms.rhbnc.ac.uk>
Date:         Thu, 25 Jun 1998 12:53:00 +1000
From: Richard Walker <Richard.Walker@CS.ANU.EDU.AU>
Sender: Mailing list for the LaTeX3 project
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
To: Multiple recipients of list LATEX-L
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
Subject:      Re: Modules
Status: R
X-Status: 
X-Keywords:                  
X-UID: 2595

Philip Taylor (RHBNC) writes:
 > How can that work?  Assuming that (e.g.) "\newcommand" is macro ->
 > {... \def ...}, then without a LaTeX equivalent of PostScript's
 > "bind", you still need access to "\def"; and if "\newcommand" is
 > macro -> {... \someconcealedversionofdef ...}, then the user can
 > use "\someconcealedversionofdef" :-(

Stick an @ in the name of the renamed \def.  That's enough to stop
most people.