:[EMAIL PROTECTED]
Sent: Wednesday, February 27, 2008 10:28 PM
To: CF-Talk
Subject: Re: Interesting idea for next CF - thoughts...
When CF6 was introduced they allowed you to add
whatever arbitrary attributes you want to cfcomponent, cffunction,
cfargument and cfproperty tags so you could use
Watch out for that though. I remember someone on this list who used to
use the extends= attribute in their cfcomponent tags. That worked
great until CF8 when Adobe actually implemented that attribute and all
their code broke. :)
You mean with an empty value?
--
s. isaac dealey ^ new
Message-
From: s. isaac dealey [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 28, 2008 8:24 AM
To: CF-Talk
Subject: Re: Interesting idea for next CF - thoughts...
Watch out for that though. I remember someone on this list who used
to
use the extends= attribute in their cfcomponent tags
You mean 'extends=' didn't actually extend a CFC? Wow, then my code was
working through magic and incantation all that time! Hot Damn, call the
Enquirer! ;)
Steve Cutter Blades
Adobe Certified Professional
Advanced Macromedia ColdFusion MX 7 Developer
_
Lol. You got me. I meant implements=, not extends=.
That was the one CF8 introduced. :)
~Brad
-Original Message-
From: Cutter (CFRelated) [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 28, 2008 8:48 AM
To: CF-Talk
Subject: Re: Interesting idea for next CF - thoughts...
You mean
Jim Davis said:
I know it won't validate, but can't you do that now?
I would expect CF to ignore any unknown attributes.
Way back when, CF5 and prior, it would throw errors on attributes it
didn't recognize. When CF6 was introduced they allowed you to add
whatever arbitrary attributes you
I've actually gone further and created my own comment tag and parsing
engine for CFC development... probably worse that this to many
people but it works wonders for me and allows me to self-document my
code pretty darn well.
Not all that far-out for those of us who've worked with Fusedocs for
Lol. You got me. I meant implements=, not extends=.
That was the one CF8 introduced. :)
Oh interfaces... that makes more sense.
--
s. isaac dealey ^ new epoch
isn't it time for a change?
ph: 503.236.3691
http://onTap.riaforge.org/blog
-Original Message-
From: Brad Wood [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 28, 2008 9:13 AM
To: CF-Talk
Subject: RE: Interesting idea for next CF - thoughts...
Watch out for that though. I remember someone on this list who used to
use the extends= attribute
As I was doing my stuff today I had an interesting idea and wondered what
others thought. In a nutshell it would be cool to be able to have a HINT
attribute for every CFML tag for VERY SHORT comments. I know this mixes
comments within logic but it would be great for certain things. For
-documenting applies at your class and method level-- not
at each individual line of code.
Interesting thought though...
~Brad
-Original Message-
From: John Skrotzki [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 27, 2008 3:13 PM
To: CF-Talk
Subject: Interesting idea for next CF
CFPARAM NAME=myVar DEFAULT=233 HINT=myHint
What would be the advanteage over simply using
CFPARAM NAME=myVar DEFAULT=233 !--- myHint --- ?
--
___
REUSE CODE! Use custom tags;
See http://www.contentbox.com/claude/customtags/tagstore.cfm
(Please send any spam
I disagree that hints are cleaner than comments. Comments are set apart
from the logic, display, whatever. They are semantically easy to parse
as ignorable by the system, remove systematically, etc. They don't
clutter the tags. They're available both in the tag-based language and
-Original Message-
From: Brad Wood [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 27, 2008 4:28 PM
To: CF-Talk
Subject: RE: Interesting idea for next CF - thoughts...
I would be inclined to simply use a regular comment. I might see value
in your suggestion if you wanted
On another note, some people programmatically remove comments and
whitespace during an ANT build/deployment. A hint attribute, for
comments, might make such a process much more difficult.
Steve Cutter Blades
Adobe Certified Professional
Advanced Macromedia ColdFusion MX 7 Developer
As I was doing my stuff today I had an interesting idea and
wondered what others thought. In a nutshell it would be cool
to be able to have a HINT attribute for every CFML tag for
VERY SHORT comments. I know this mixes comments within logic
but it would be great for certain things. For
On Wed, Feb 27, 2008 at 6:43 PM, Dave Watts [EMAIL PROTECTED] wrote:
My problem with comments in general is that I often see them used to
describe things that are self-describing,
I tend to agree with Dave. IMO comments should tell ppl the what and why you
are doing something.
I have been a
Jim Davis said:
I know it won't validate, but can't you do that now?
I would expect CF to ignore any unknown attributes.
Way back when, CF5 and prior, it would throw errors on attributes it
didn't recognize. When CF6 was introduced they allowed you to add
whatever arbitrary attributes you
18 matches
Mail list logo
