Re: [Wesnoth-dev] A WML idea: import

[Yann Dirson]

On Mon, May 09, 2005 at 05:00:41PM -0500, David White wrote:
> Guillaume Melquiond wrote:
> 
> >On 5/8/05, David White wrote:
> > 
> >
> >>Perhaps we can add a simple module system to Wesnoth very easily: by
> >>adding a WML command called 'import'. It would work something like this,
> >>
> >>import "path"
> >>
> >>Any thoughts?
> >>   
> >>
> >
> >I have one concern. User campaigns (as do mainline campaigns) rely on
> >some core macros; for example MENU_IMG_TXT. If imported, the campaigns
> >won't know about these macros (it's even worse, they redefine them
> >then, because they believe it is an old Wesnoth version). So the user
> >campaigns would have to preprocess the core macros too, in order for
> >them to be available. This is not an issue: it would not be the first
> >change to WML that is not backward compatible. But I was wondering if
> >you had another solution in mind in order to deal with the #defines.
> > 
> >
> Yes, my solution to that was the same as yours: they would have to 
> preprocess the core macros too, by specifying 'standard' Wesnoth cfg 
> files to {include}.
> 
> This would be somewhat inefficient, but how bad it would be I'm not sure.

The time to build the cache on ipaq is already very important today
(several minutes).  Although I have not looked in details where the
problem lies, I suspect such a change would not make things better in
this respect.

-- 
Yann Dirson    <address@hidden> |
Debian-related: <address@hidden> |   Support Debian GNU/Linux:
                                    |  Freedom, Power, Stability, Gratis
     http://ydirson.free.fr/        | Check <http://www.debian.org/>