DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35839>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35839 ------- Additional Comments From [EMAIL PROTECTED] 2005-08-09 04:15 ------- (In reply to comment #13) > Created an attachment (id=15947) --> (http://issues.apache.org/bugzilla/attachment.cgi?id=15947&action=view) [edit] > Proposed new parser > > Reworked parser based on the tapestry template parser. > In what respect is this parser "based on the tapestry template parser" -- cut-n-paste code? If so, that's better than adding an explicit dependency for what will likely end up being a core part of Shale ... in the long term it would be better if the parser were factored out into a reusable module (perhaps in Jakarta Commons) so we could share it. I do object to one particular technical detail -- I do not like the "IXXX" convention (which Tapestry, among other projects, uses) for interfaces. That's inconsistent with coding conventions throughout the rest of Shale. I was a big fan of Hungarian notation in C when I was using dumb text editors ... it doesn't add enough value in an O-O language (with modern tools) to make up for the fact that my eye stutters over it every time I see it). > AFAIK there is one incompatibility to the current parser. All tags with > a jsfid (implicit or explicit) that are not ignored must be well formed. > Does the Tapestry parser have the same sort of restriction (for jwcid)? If so, it's not a fatal flaw IMHO (essentially, JSP imposes the same restriction on custom tag elements), but I'm curious. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
