> CFIF..CFELSEIF..CFELSE tags that was XML compliant...
> Totally
> optional, but available to use if you need XML compliant
> CFML for some
> reason.
> Of course, that's remarkably off-topic, but the hope that
> that might
> sometime exist is another tangible reason to always quote
> your
> attributes. Plus it makes your CFML more consistent with
> the (X)HTML
> that it's likely embedded in. Same deal with closing
> slashes on empty
> tags (CFSET, CFTHROW, etc).
Though I use a lot of cfscript...
I'd end up with a lot of this:
<cfscript>
//<![CDATA[
... my code here ...
//]]>
</cfscript>
and any purpose there might have been for using an xml parser against
my cfml would be made moot by the fact that about 90% of my code looks
like this. :)
s. isaac dealey 954.927.5117
new epoch : isn't it time for a change?
add features without fixtures with
the onTap open source framework
http://www.sys-con.com/story/?storyid=44477&DE=1
http://www.sys-con.com/story/?storyid=45569&DE=1
http://www.fusiontap.com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
