So, are people just not running into this because they don't do any external
"work" in their pseudo-constructors? Are they just accepting that it's a
fact of life? Are they unaware of the potential for badness? Is there a
work-around I'm unaware of?
We have a couple of CFCs that cannot be viewed through the cfcexplorer because of work they do in the pseudo-constructor but they are the exception (they do security-related things to prevent the CFCs being instantiated except by authorized users - they're part of our membership subsystem which is very tightly locked document). We are generally very careful to do nothing beyond simple instance variable initialization in the pseudo-constructor.
Regards, Sean
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
