It's easier because the tool shipped by MACR looks up the metadata for the CFC and displays it. You could, of course, build a tool to generate docs from Custom Tags (or UDFs, see UDFDoc at cflib.org) as long as you followed a standard.
======================================================================== === Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc (www.mindseye.com) Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia) Email : [EMAIL PROTECTED] Blog : www.camdenfamily.com/morpheus/blog Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Brad Howerter > Sent: Tuesday, September 02, 2003 8:23 AM > To: '[EMAIL PROTECTED]' > Subject: RE: [CFCDev] Display in CFCs > > > True, but it is easier to document a CFC than it is to > document a custom tag. > > -----Original Message----- > From: Massimo, Tiziana e Federica [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 30, 2003 1:08 AM > To: [EMAIL PROTECTED] > Subject: Re: [CFCDev] Display in CFCs > > It's not like a CFC automagically document itself, a lazy > developer can easily avoid to specify return type and hint > attributes and you are left without any documentation. CFC > sort of standardize and automate extracting documentation, > but there is nothing like true "self documenting" (same for JavaDoc). > > If you care about documenting your stuff, there would be no > differences between CFC and custom tags, if you don't care... > You will likely end up with a mess anyway :-)) > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
