X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1528" "Thu" "2" "July" "1998" "22:51:12" "+0200" "Frank Mittelbach" "Frank.Mittelbach@UNI-MAINZ.DE" nil "39" "Re: stop please" "^Date:" nil nil "7" 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 XAA21693; Thu, 2 Jul 1998 23:09:32 +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.8AC4ADE4@listserv.gmd.de>; Thu, 2 Jul 1998 23:06:43 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 377119 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 2 Jul 1998 23:05:49 +0200 Received: from kralle.zdv.Uni-Mainz.DE (kralle.zdv.Uni-Mainz.DE [134.93.8.158]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id XAA18312 for ; Thu, 2 Jul 1998 23:05:36 +0200 (MET DST) Received: (from Ufrank@localhost) by kralle.zdv.Uni-Mainz.DE (8.8.8/8.8.8) id XAA25938 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 2 Jul 1998 23:05:36 +0200 (MET DST) X-Authentication-Warning: kralle.zdv.Uni-Mainz.DE: Ufrank set sender to latex3 using -f Received: (from latex3@localhost) by frank.zdv.uni-mainz.de (8.6.9/8.6.9) id WAA01209; Thu, 2 Jul 1998 22:51:12 +0200 References: <199807011148.NAA04935@relay.urz.uni-heidelberg.de> <199807012142.XAA16990@frank.zdv.uni-mainz.de> Message-ID: <199807022051.WAA01209@frank.zdv.uni-mainz.de> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: Date: Thu, 2 Jul 1998 22:51:12 +0200 From: Frank Mittelbach Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: stop please Status: R X-Status: X-Keywords: X-UID: 2643 Hans writes: > Why bother about voting if you are the man? :-) you may be right that this is like voting with my kids (they have two each and the parents have one) > >..the specification says \_: and it is as > >trivial as changing / to something else to replace \\[a-zA-Z]+_ by > >\\[a-zA-Z]+/ and i'm happy to do this if there is a need for this, > > Clearly not as it excludes those who want to experiment with submodules... com'on. with a spec as is you can experiment with modules if you really want to as easily as with some other. just introduce / as a sub-module separator in the first word. you may be right that it would look perhaps look ugly but it would work without any problem and would prove either me or you wrong. so \foo_bar:nn would be module foo function bar and \foo/baz_bar:nn would be module foo submodule baz function bar so what? (and it doesn't look so bad actually) just to change all the files to some new convention takes some effort which can be better spend. at the moment at least! > > eg > >if you prove me wrong and your module/submodule mechanism can be made > >workable in practise or if after experiencing with the code i got > >enough people (that used it) saying that they feel \foo/bar:nn is > >better readable to them than \foo_bar:nn > > ...and then nobody will bother developing it. :-) too bad, but i claim it is a red hering. it is simply easier to abstractly talk about such things instead of doing the nitty gritty work. frank