Perhaps the phrase "unreadable" was not meant to refer to the human act
of reading.
I have experienced some entities - with a large development staff - that
need to enforce a set of coding standards. They employ scripts that will
parse (or "read") a developer's cfm file - when checked in - apply a
long sequence of regular expressions to insure that the code follows
their standard, and spit out a QA report.
Having a bracketed tag nested within another one could present a problem
there. It also could be at odds with some XML/XHTML/W3C spec that I'm
too lazy to research right now.
There are two opinions at odds here: 1) OpenBD's CFML should behave
exactly like Adobe's CFML, and 2) Nesting a bracketed tag within another
one is not a correct practice. Tags should contain attributes.
I've spent enough time on this list to realize that opinion 1) is not
considered as some "prime directive" here - especially when another
opinion has a reasonable amount of merit.
Al Holden
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
online manual: http://www.openbluedragon.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
