Kevin Brubeck Unhammer <unham...@fsfe.org> writes: > "Jimmy O'Regan" <jore...@gmail.com> > writes: > >> [Readding list cc] >> >> On 13 July 2013 07:12, Mikel Forcada >> <m...@dlsi.ua.es> wrote: >>> Sergio, Jimmy, all: >>> >>> Thanks for your help. I am, however, still a bit confused. >>> >>> Jimmy says that "it's no less counterintuitive to pass <clip> when you want >>> <b>.". Well, I was just passing positions and hoping that pos="n" accessed >>> the blank between the lexical units at pos="n" and pos="n+1", as this is >>> what you do when you don't use macros: >> >> I'll take a step back here, and admit that "no less counterintuitive" >> is simply incorrect. I was swept up in the moment a little; what I >> really meant is that both are counterintuitive (albeit, to different >> degrees) and if we are to consider this a bug, then the correct >> resolution would be to do what is intuitive: to allow <b> as a >> parameter to macros. The correct++ resolution would be to allow >> anything that can appear in <out> to be used as a parameter to a >> macro. > > Is there a good reason why we can't pass anything to a macro?
Here's one: would the arguments to a macro still be referred to as clips
within the macro? Ie. will a <var> or a <lit-tag> or <b> etc. within the
macro be referred to with clip pos=n part=stuff? What then happens if
someone writes a macro saying
<out><lu><clip pos="1"/><b pos="1"/><clip pos="2"/></lu></out>
meant to be called as
<with-param><clip pos="1"/><clip pos="2"/></with-param>
but the caller messes up:
<with-param><b pos="1"/><clip pos="2"/></with-param>
That doesn't look good. Does this output the <b> twice or just once? Or
should the compiler complain and demand that passed <b>'s are referred
to with <clip> while in-between-<b>'s are referred to with <b>?
--
Kevin Brubeck Unhammer
GPG: 0x766AC60C
pgpAnTGr7uyBQ.pgp
Description: PGP signature
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
