In general, there is no point in abbreviating the names while loading a
module: One loads them in full and then, as needs arise, one use local,
more convenient definitions. This way the user can use different kinds of
mixtures of modules in different localities.
One example might be when putting together different manuscripts of
different authors: Each author might have a different blend of say the math
or phys module. By not abbreviating the names when loading those modules,
the different manuscripts will not clash.
(So, in particular, I think that LaTeX3 should make the environment
"document" to a locality, and the definitions of that document that the
user might add should be made within that environment: The commands that
need to be global should be named \document/<document name>/<command name>.
Then the commands of different documents will not clash when run together.)
At 21:00 +0200 98/06/20, Volkan Yavuz wrote:
>* Specifying the Local Scope
>after this declaration, all macros that are \newcommand'ed within this
>package are auto-magically prefixed with something like
So a command like this could be useful to load all macros in
latex3/contrib/math, but it would not abbreviate the names. Instead an user
would define a special environment which abbreviates the names. Inventing
and as long as the locality is valid, names \m/foo would expand to
One reason for doing it this way is that it is difficult know in advance
what kind of blends of modules users may make use of.
Then one could of course think of more complicated things (like search
paths etc), but I think this would suffice quite far.
* Email: Hans Aberg <mailto:[log in to unmask]>
* Home Page: <http://www.matematik.su.se/~haberg/>
* AMS member listing: <http://www.ams.org/cml/>