X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil]
	["1443" "Tue" "23" "June" "1998" "11:34:20" "+1000" "Richard Walker" "Richard.Walker@CS.ANU.EDU.AU" nil "26" "Re: Modules" "^Date:" nil nil "6" nil "Modules" 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 DAA09246;
	Tue, 23 Jun 1998 03:34:38 +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 <5.4E835F55@listserv.gmd.de>; Tue, 23 Jun 1998 3:34:35 +0200
Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE
          (LISTSERV-TCP/IP release 1.8b) with spool id 368063 for
          LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 23 Jun 1998 03:34:31 +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 DAA15307
          for <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>; Tue, 23 Jun 1998 03:34:27
          +0200 (MET DST)
Received: (from richard@localhost) by ricetub.anu.edu.au (8.8.2/8.8.2) id
          LAA12465; Tue, 23 Jun 1998 11:34:20 +1000 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <v03110707b1b3e8ee533c@[130.237.37.30]>
X-Mailer: VM 6.29 under Emacs 19.34.1
Message-ID:  <199806230134.LAA12465@ricetub.anu.edu.au>
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
In-Reply-To:  <v03110707b1b3e8ee533c@[130.237.37.30]>
Date:         Tue, 23 Jun 1998 11:34:20 +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: 2588

Hans Aberg writes:
 >   So it is possible to have a lower, development level code that works
 > entirely different from what is the case now, but on top of that building
 > development or user levels which work pretty normal, relative to the
 > already existing TeX and LaTeX2e standards.
 >
 >   But then with this new, entirely new lowest development level code, it
 > will be possible to add entirely new standards of producing code. Then
 > these new ways will be orthogonal to the old LaTeX2e/TeX standards, so that
 > these do not conflict.

Well, we already have this to some extent.  The @ symbol becomes a
normal letter while reading cls and sty files.  In the new regime we
also make _ and / into letters.  That means you get to keep the normal
meanings of _ and / while processing documents (highly desirable).

 >   One idea one might explore is a TeX environment: It has all the old TeX
 > names defined locally within that environment, but those definitions expand
 > to the global \tex/<command name> definitions.

This is akin to 2.09 compatibility mode.  With smart editors you don't
need it.  I am happy to have a keystroke in my editor insert \tex/ for
me (and perhaps display it in a different colour?)  If you don't want
the clutter, you might (in a smart editor like Emacs) hide the long
prefixes (either altogether - displaying the result in a different
colour, or hide the prefix as `...' - as is done with outlining).