I don't think that we want to "get" a definition outside of the container. That should be an implementation detail of the container. I think it's this philosophy that allowed the tags to be cleaned up significantly.

Instead, attributes are now "recognized" as being a definition and thus the container is invoked by the render tag in order to perform the render.

Perhaps we're talking past each other, do you have a test case that shows the failure?

David



Antonio Petrelli wrote:
David H. DeWolf ha scritto:
Works for me. . .go for it!

Committed but there's still a problem. In previous versions, if the attribute value was a string and the type was "definition", it tries to get that definition and put it as the value of the attribute. This logic seems to have disappeared. I put a FIXME for it, because i don't know the new "correct" way to get a definition.

What do you think?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to