I use a few of those, particularly abstract, deprecated, and throws, though I use my deprecated attribute as a flag (present means deprecated), so that the value can be information about the deprecation (date of deprecation, recommended alternative, etc) so that the documentation can have that information.
I'm not using getMetaData() though, I use a parser-based documentor that Spike Milligan wrote and I've extended. In many ways, its a runtime-javadoc for CFCs. I'm not sure where you can download it, but perhaps Spike will chime in? cheers, barneyb ----- Original Message ----- From: John Temm <[EMAIL PROTECTED]> Date: Fri, 20 Aug 2004 14:04:12 -0400 Subject: [CFCDev] Additional documentation attributes for CFC, CFArg, CFFunc To: [EMAIL PROTECTED] Hi In one system I have been working on, I have created a standard set of additional attributes that I place in all of my CFC tags to increase the granularity of the docs for the API. I include these below for interest. I am wondering if anyone else is doing something similar and if anyone has ideas for additional attributes or other ways of doing similar. All these attrib's are accessible with getMetaData(). Cheers Chip Temm -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words '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]
