Moritz Goebelbecker <[EMAIL PROTECTED]>:
> Am Monday, 09. April 2007 19:34 schrieb Eric S. Raymond:
> > The thing I most want abolished is the option to have the WML
> > autocomplete the file extension. Or, to put it another way,
> > macroscope needs all image file references to be detectable in a
> > context-independent way with a regular-expression match, rather than
> > by requiring a WML-aware parse of the file. The easiest way to do
> > this is to require that all references have one of a small set
> > of recognizable suffixes like ".png", ".wav", ".ogg", and ".jpg".
> > Adding to that set of extensions is not a big deal, but the set
> > has to exist for any tool like macroscope to have a prayer of working.
>
> This will not work in any case where the actual image name is
> constructed from (one or more) parameters inside a macro. One very
> common case are rotations in terrain WML:
>
> | [image]
> | layer={LAYER}
> | [EMAIL PROTECTED]
> | [/image]
> | rotations=n,ne,se,s,sw,nw
>
> So a macro call like
>
> | {SOME_TERRAIN_MACRO some/image.png}
>
> would result in image names like some/image.png-se which is obviously wrong
> and wouldn't help with reference checking at all.
I think I understand the problem. But is there some reason the above
couldn't be written like this?
[image]
layer={LAYER}
name={IMAGE} # Which had better contain the string @R0
[/image]
rotations=n,ne,se,s,sw,nw
{SOME_TERRAIN_MACRO some/[EMAIL PROTECTED]
Not only would that plant a reference in the right place from macroscope's
point of view, the @R0 in the call would be a valuable clue to the reader.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
signature.asc
Description: Digital signature
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
