QuackFuzed [ Ramblings of a Con..ColdFuzed Mind ]

Learning CF9: Buh Bye Comment-Based Attributes

Posted on December 18, 2009 at 4:32 PM in ColdFusion

In my previous entry I discussed the use of comment-based attributes for the new all-script CFCs in CF9 and what it actually takes to make them work as advertised. As Andy Matthews pointed out in a comment on the post, they aren't technically "comments" in a traditional sense, but rather are JavaDoc notations.

After spending a bit of time weighing the arguments both for and against the use of comments as executable code, and playing with using them and not using them, I have conclusively sided with the "comments as executable code are pure evil" group. Why?

[Continue Reading]

Comments

(Comment Moderation is enabled. Your comment will not appear until approved.)

On 12/18/09 at 5:24 PM, Henry Ho said:

output=false is almost useless unless you're calling cfc in CFML style or you're calling 3rd party code that calls writeOutput() somewhere. Generally, output=false can be skipped.

I agree, "comments as executable code are pure evil", but for hint, I think that's fine. However, hint is still cleanest in /** */ comment block IMO. Just don't put cf-orm/hibernate annotations there, you don't get code insight in CF Builder if you use the comment block way.

On 12/18/09 at 7:20 PM, Dan Vega said:

The great thing is your are not limited to a certain style. I for one love the Java doc syntax and find it much cleaner that the approach you have here. To each his own right! In the end is less verbose that tab based components and thats what makes me happy!

On 12/18/09 at 7:45 PM, Dan Vega said:

As I learned yesterday as well putting extends in java doc won't give you code insight into the super class. I am going to file a bug for both of those though because if it's valid builder should pick it up!

[Add Comment]