Re: [Webmacro-devel] Handling Dreamweaver stuff

[Lane S. <la...@op...>]

or
#macro.MacroName(arglist)
just a thought.

macros are not in widespread adoption. It would impact me probably the 
most. I can live with what we decide is the cleanest solution.

Personally, I would rather not fool with macro invocation syntax and 
just allow an unknown directive to pass through when strict type 
checking is off.

-Lane

kea...@na... wrote:

> It occurs to me that the white space issue may not be a big deal, 
> since the whole unknown directive handling problem is mainly just an 
> issue for HTML generation (DreamWeaver, et al), where white space 
> isn't significant.  Ergo, my initial suggestion may not be too 
> terrible, ie, just dump the directive name and arg list out (and don't 
> worry about lost white space).
>
> Another approach, which would be cleaner but not backwards-compatable, 
> would be to change the syntax for macro invocation.  For example, if 
> macros calls started with #$macroname or, Velocity-like: #(macroname), 
> the parser could determine what is a valid directive and could decide 
> what to do about other things that look like directives at parse time.
>
> Keats
>
>  
>

-- 
Lane Sharman
http://opendoors.com Conga, GoodTimes and Application Hosting Services
http://opendoors.com/lane.pdf BIO