Re: Actual libtool support routines

Adriaan de Groot wrote:

> On Thursday 28 August 2003 15:30, you wrote:
> > The simplest method would be to require something like ":import libtool".
> > We can make a collection of these optional modules.
> 
> I'd go for that, with an :import command which would look for libtool.aap 
> (just like default.aap) in some standard places. You can use :ltlib without 
> any penalty without importing the module, it's just that AAP will complain 
> that there is (say) no compile action defined for ltlibobjects when it comes 
> time to build something.
> 
> :import should work a lot like :include, but only search in system places.

It is starting to look like a good idea.  Thinking ahead for the future
with hundreds of modules available (well, _far_ future), do we need
to do something with scopes for imported modules?  The ":include"
command uses the current scope of the recipe, perhaps for ":import" the
imported module should have its own scope, so that it can have local
variables.  This would be important when doing the ":import" from
several recipes in a recipe tree.  You wouldn't want to libtool module
to use the scope of several recipes, do you?

> > Could this mechanism be automated?  Thus as soon as something related to
> > Does this sound too complicated?
> 
> It does; in particular since you'd have to recognize things like
> LIBADD (which might be a libtool thing) and every other subtlety of
> libtoolism. Perhaps using :ltlib should automatically load the libtool
> module, but in general I'd say that the penalty of having to do 
> 
> :import libtool
> 
> in recipes for libtool is small; especially since other build weirdnesses 
> might have a similar structure (:import distcc, anyone?),

Let's not make it automagical.  The ":ltlib" command is a high-level
command for which it is logical that you always need the libtool module,
thus automatically doing a ":import libtool" sounds acceptable.  But
importing a libtool module when a "ltobject" filetype is used somewhere
is too much magic.

Are you going to make that libtool module?  Then we also need the
":import" command.  Earn a few more Zimbu award points!

-- 
hundred-and-one symptoms of being an internet addict:
257. Your "hundred-and-one" lists include well over 101 items, since you
     automatically interpret all numbers in hexadecimal notation.
     (hex 101 = decimal 257)

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf