Sorry to contadict you Adrian, but I can say with complete conviction
(and no explanation at all) that these experiences did happen...I know that obviously
a variable either exists or doesn't. That
doesn't mean that in every instance a function will work though. I replaced the
isdefined function (after checking to be sure the
syntax was correct) with parameterexists and it worked. I switched it back to
isdefined and it did not. I did it in more than one
instance and I confirmed the issue and verified the results of the workaround with
other cf programmers on site.
Why would I say the problem did arise and have such a simple a workaround if it was
a figment of my imagination or some other
underlying issue totally seperate from the cf function? I do not remember what version
of CFAS or on what platform it was running
(I do know it wasn't 4.5x. I also no longer have the exact pages where I had the issue
off the top of my head. I have been
programming in cf for 5 years now so the jobsites where the pages reside are not
necessarily available to me now.... anyway I
replaced the isdefined function on them anyway so I couldn't find them even if I had
access. All I am saying is that you cannot
tell me what happened or that it could't without working on the applications I did in
the environment I was working in.
I always say "if it doesn't work do what it takes to corrrect it" In this case I did
not get stuck on the fact that the problem
was totally illogical. I simply made it work. In this case it was as simple as a
change of function.
I have seen postings up here for issues that should never have come up logically
speaking yet they do. I would think it is more
productive to say "that is an interesting issue...how did it happen" in any of these
cases. Than to say "that can't happen
because...." Whenever I try that one on the users of applications I have worked on I
am reminded that I do not have all the
answers.
sorry about the typo I hope I won't be graded on it ;-)
Frederic
Aidan Whitehall wrote:
>
> Oh yeah, I have the same problem. Sometimes functions work and sometimes
> they don't. I reckon it depends on the weather...
>
> Sorry to be sarcastic, but how can you say "most of the time it worked but
> in some instances it seemed not to" with any conviction? Variables either
> exist or they don't; there's not a lot of scope for anything in-between.
>
> > I am
> > sorry to see parameterexists() depreciated.
>
> I'm not. It's more to type ;-)
>
> And it's "deprecated", BTW. Depreciation is what your car does over time.
>
> --
> Aidan Whitehall <[EMAIL PROTECTED]>
> Netshopper UK Ltd
> Advanced Web Solutions & Services
>
> http://www.netshopperuk.com/
> Telephone +44 (01744) 648650
> Fax +44 (01744) 648651
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
