At 12:28 PM 11/5/2001, you wrote:
> > I still disagree, why should my greater application have or want to know
> > anything about how serviceAvailable() and related UDFs do the job they say
> > they will ?
>
>When I first started CF I couldn't believe that I didn't have a way to call
>a function o
> I still disagree, why should my greater application have or want to know
> anything about how serviceAvailable() and related UDFs do the job they say
> they will ?
Because that's the way it is. You have two choices -- adapt your thinking
and implement it the way that it works currently, or do
At 10:30 PM 11/2/2001, you wrote:
>
>If serviceAvailable() requires the use of the external variable
>application.services I would say that it is a Bad Thing (TM) if you can
>invoke it like serviceAvailable('borkyService'). The UDF should be
>modified so it has to be invoked by sending all externa
> At 02:37 AM 11/2/2001, Birgit wrote:
>
>>Pete,
>>you are right concerning but I can't see the limitations
>>regarding UDFs.
>>
>>A UDF pre se is meant to be self-contained and therefore not relying on
>>anything outside it's
>>own scope. Wouldn't the use of shared data inside a UDF be
I don't think so... take for example the following
if locking could be done in
do stuff, we don't care about how serviceAvailable() does it's
job, just that we ask for a service and it
tells us if it is available
internally, serviceAvailable must perform a named l
Pete,
you are right concerning but I can't see the limitations
regarding UDFs.
A UDF pre se is meant to be self-contained and therefore not relying on anything
outside it's
own scope. Wouldn't the use of shared data inside a UDF be defeating this
purpose?
You could read a shared scope variable
Nope. It's a big limitation for CFSCRIPT and UDF's
+
Pete Freitag ([EMAIL PROTECTED])
CFDEV.COM
ColdFusion Developer Resources
http://www.cfdev.com/
-Original Message-
From: James Sleeman [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 0
7 matches
Mail list logo
