X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1415" "Thu" "25" "June" "1998" "18:19:44" "+0200" "Hans Aberg" "haberg@MATEMATIK.SU.SE" nil "29" "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 SAA10561; Thu, 25 Jun 1998 18:20:39 +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 <10.698C51A0@listserv.gmd.de>; Thu, 25 Jun 1998 18:20:36 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 371209 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 25 Jun 1998 18:20:30 +0200 Received: from mail.nada.kth.se (root@mail.nada.kth.se [130.237.222.92]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id SAA21538 for ; Thu, 25 Jun 1998 18:20:28 +0200 (MET DST) Received: from [130.237.37.112] (sl36.modempool.kth.se [130.237.37.56]) by mail.nada.kth.se (8.8.7/8.8.7) with ESMTP id SAA22307 for ; Thu, 25 Jun 1998 18:20:26 +0200 (MET DST) X-Sender: su95-hab@mail.nada.kth.se Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <980625145808.48d9@vms.rhbnc.ac.uk> Date: Thu, 25 Jun 1998 18:19:44 +0200 From: Hans Aberg Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Modules Status: R X-Status: X-Keywords: X-UID: 2598 At 14:58 +0100 98/06/25, Philip Taylor (RHBNC) wrote: >>> I guess there will be a command called \tex_def or \tex/def or something, >>> which one can use. > >Indeed, that was my very point : David was suggesting that \def could >be made inaccessible by the format; I argued that all the while TeX lacks >the equivalent of PostScript's "bind", primitives which are used by >maos defined in the format source and which must be accessible to >the user code can never be made totally inaccessible. You can "hide" >them but you can't remove them, so why bother even to hide them if an astute >programmer can work his way around the hiding mechanism? I think the idea should be to help indicating objects proper use. >(the earlier proposal to use commercial-at is just one way of hiding such > things, neither better nor worse (in this context) than any other mechanism). For use with modules, my suggestion is that @ should be used for indicating that a command is "private" or "protected", that is not for external use of that module. So the command should then be named \tex/def and not \tex/@def, as some other module is going to use it, like other modules defining \/new. Hans Aberg * Email: Hans Aberg * Home Page: * AMS member listing: