- Subject: Re: Jörg's LaTeX mode r100
- From: "G. Milde" <milde@xxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 8 May 2007 09:36:25 +0200
On 7.05.07, Jörg Sommer wrote:
> Marko Mahnic <marko.mahnic@xxxxxxxx> wrote:
> > G. Milde wrote:
> >
> > From the programmers perspective it is better to split a large package
> > into many smaller files even if they are always loaded. The
> > package is easyer to maintain. (imagine jed code in one large C file ...)
> ACK.
> > It would probably also make sense to put larger modes into separate
> > subdirectories of lib.
This is already possible without much effort. All files that are not
meant for general use could go to a directory "latex-jlm/" and be
evaluated with a line like
() = evalfile("latex_jlm/commands", current_namespace());
in latex.sl. I would leave the main file in separate, so it can be
initialized by the usual
require("latex");
or
autoload("latex_mode", "latex");
but this is a matter of taste.
> > > > This is just a suggestion since I think there is no such thing as
> > #include in slang, but it might be worth considering.
> I second this idea, because I wish :) an included file goes into the same
> (private) namespace as the main file.
This should work also for anonymous namespaces, i.e.
#include <somefile>
would replace the directive by the content of <somefile> (searched along
the jed library path) and proced with the pre-parsing, right?
I second an #include preprocessor directive, as I expect one slc file
will load faster than several ones...
Günter
--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.
[2007 date index]
[2007 thread index]
[Thread Prev] [Thread Next]
[Date Prev] [Date Next]