What about non-custom tags that have this ambiguity? CFHTTP, for example. Or CFINVOKE. There are quite a few places that a XML self-close clears up ambiguity.
And everywhere else, unless you use self-closes throughout, you still have to read and interpret the tag name. I.e. <cf_tag /> obviously has no closing tag, because of the slash. However, <cfset x = 5> might, unless you actually read the "cfset" part, recall that CFSET doesn't take a body, and therefore it has no closing tag. Easier to just throw the slash in there and know without having to do any extra thinking. cheers, barneyb On 7/28/05, Ben Rogers <[EMAIL PROTECTED]> wrote: > > Especially when reading a cfmodule. (bad, I know. Not my code). > > I would argue that all custom tag calls, whether they are made with the > cfmodule tag, using cfimport or cf_tagName syntax, should either include a > closing tag or use the XML style trailing slash. Doing so clears up a lot of > ambiguity. The only exceptions I make are for poorly coded tags that haven't > been properly coded to handle the end tag execution state. > > That said, in all other cases, I prefer not to use the XML style trailing > slash because it serves no purpose. > > Ben Rogers > http://www.c4.net > v.508.240.0051 > f.508.240.0057 > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
