I guess its all just one step towards being compliant with xml, all you would have to do to make it really compliant is something like the following to get around the issue with cfelse.
<cfif 1 EQ 1 > test <![CDATA[ <cfelse> ]]> </cfif> -- Taco Fleur Senior Web Systems Engineer http://www.webassociates.com -----Original Message----- From: Barney Boisvert [mailto:[EMAIL PROTECTED] Sent: Friday, 4 February 2005 9:25 AM To: CF-Talk Subject: Re: cfset ? Except that CFML isn't XML compliant. CFELSEIF and CFELSE, in particular, are an issue. If you use CFSWITCH for all conditionals with more than one block, then it'd work (you can still use CFIF without a CFELSE). cheers, barneyb On Fri, 4 Feb 2005 09:20:43 +1000, Taco Fleur <[EMAIL PROTECTED]> wrote: > Its just to make the code xml compliant, basically you could > eventually parse a cfm page and work with it as XML.. > > -- > Taco Fleur > Senior Web Systems Engineer > http://www.webassociates.com > > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:193014 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
