> Yesterday, I was able to reliably reproduce a nice, juicy "You are
> attempting to dereference a scalar..." error with the Duplicate(cfcatch)
> statement - a known issue with the 6.1 updater.  However, upon logging
> into my system today, MX seems to have forgiven the issue and now happily
> accepts the statement.
>
> Now, since magic unfortunately doesn't exists and the jury's still out
> on whether our computers actually mess with us on purpose, there's
> obviously a key in the CFCATCH structure that's a string that was being
> referenced yesterday that isn't being referenced today.

Computers are way too stupid to do anything on purpose, so you can count
that out.

If you catch different exception types, they may contain different things.
This is especially true in CFMX, where the exception object is essentially a
wrapper of some Java object. There are some articles about this on Sean
Corfield's and/or Brandon Purcell's blogs, I think.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to