Re: Actions, routes and builders in general

On Thursday 03 June 2004 21:30, Bram Moolenaar wrote:
> A related issue is that the ":route" command is a bit strange, in that
> it defines how to turn one filetype into another and then lists the
> names of the actions to be taken.  This is very unusual, no matter what
> background you have.

Yes - ideally, AAP would find the right route itself, based on the filetypes 
of the sources and the target type.

> The basic idea of a Builder is that it specifies how to build a target
> from sources of a certain type.  For example: How to build an object
> file from a lex file.  Or how to build a dllobject file from a C++
> source file.
>
> Besides the building itself, the Builder can be asked to return the
> supported types.  Both for sources and for targets.

OK, I suppose. But what do you use for source and target types? The builder 
for executable-program can take sources of type object-file. Oh, and .res if 
you're using the windows toolset -- I can see how that works. Useful.

> I think it should be possible to have the :action and :route commands
> create a Builder object.  This provides backwards compatibility without
> doing everything twice.

Sounds neat.

-- 
   "On top of that [watching KDE CVS] is interesting in a perverse 
    way, like watching sausage get made. By very smart people." - dkite


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504