As far as I can tell querynew function accept a columnlist as and argument which is required and that could be the reason of querynew() failing.ThanksQasimOn 3/31/06,
Jim [EMAIL PROTECTED] wrote:
cfargument ...default=#queryNew()#/insead ofcfargument
yes
regards
salvatore
- Original Message -
From:
Qasim
Rasheed
To: CFCDev@cfczone.org
Sent: Thursday, April 06, 2006 3:31
PM
Subject: Re: [CFCDev] max number of
argument to init method
As far as I can tell querynew function accept a columnlist as
and
On 4/3/06, Gary Menzel [EMAIL PROTECTED] wrote:
. strong typing could easily be an option that could be enabled or
disabled by a setting (either through a tag or through the CF Administrator)
even in complete isolation to interfaces .
If programmers ruled the world, we wouldn't need
It should be a page-level or function-level directive.
cfsettting strongtyping=true
Roland
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Patrick McElhaney
Sent: Thursday, April 06, 2006 3:49 PM
To: CFCDev@cfczone.org
Subject: Re: [CFCDev] Mixins vs.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Peter Bell
The fact is that components only take you so far for reuse anyway. Even if
you use strong typing and interfaces, components don't specify how errors
are handled, they don't explicitly document
Hi Roland,
But how do you fully describe all of the possible errors and the difference
between warnings and fatal errors (if it is a warning you might not want to
cfthrow)? Of course, you can put any information in a hint, but it doesn't
mean that people will do it consistently or
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Peter Bell
But how do you fully describe all of the possible errors and the difference
between warnings and fatal errors (if it is a warning you might not want to
cfthrow)? Of course, you can put any
Hi Roland,
Appreciate all the ideas, guess we're looking at this from two different
perspectives summed up in your last sentence:
I don't know of ANY API that is usable without proper documentation.
We're looking for machine level reusability - without any human
intervention, so our approach
On 4/6/06, Roland Collins [EMAIL PROTECTED] wrote:
It should be a page-level or function-level directive.
cfsettting strongtyping=true
Isn't it already a function-level directive? You can set
returntype=any on cffunction and type=any on cfargument.
Can you give me a concrete example of what
Well you're really describing a perfect use for Interfaces if you're talking
about that type of reusability. Other languages do provide great constructs
for dealing with all of the problems that you describe. Java allows you to
define the types of exceptions that can be thrown, for instance.
It's about more than just the return type.
For instance, this is perfectly valid in cf:
cfset myQuery = QueryNew(columns go here)
cfset myQuery = Woohoo! This used to be a query - now it's a string!
That's all because of loose typing. In fact, in CF, you can do this:
cfset myQuery =
Agreed, it actually requires a little more than just interfaces though. For
example, the optional methods for one class may be dependent on optional
attributes from another class so you also need a whole level of generation
level dependency management (can't have a FedEx shipping method if you
12 matches
Mail list logo
