Re: Patch and test to allow component calls

On Wed, 22 Sep 2004, John Williams wrote:

> So is your only objection that our current design does not allow us to
> implement it cleanly enough?

Well, I don't feel strongly that this feature _is_ needed, but I don't
object to it all that strongly.  It's yet another special case, since it
won't work when the path is a Perl expression.

And really, how different is this from most languages, like Perl:

 if ( ... )
 {
     if ( ... )
     {
         # lots of code
     }
 }

The closing braces have no indication of what they close.

> I wouldn't put the decision of whether the ending tags matches the
> beginning tag in the parsing code anyway.  It needs access to the
> comp_with_content_stack, which is in the compiler.
> Compiler::component_content_call_end is where I put it last time.
> The parser just passes anything after '</&' to the compiler,
> and it makes the decision whether it is valid.  No back and forth.
>
> Also, as Jonathan pointed out, the definition of whether it is a literal
> is well-documented in the manual, so I don't think the the design will
> suffer very much if we put [\w/_.] in more than one place.

True.


-dave

/*===========================
VegGuide.Org
Your guide to all that's veg.
===========================*/


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php