Title: RE: [CFCDev] Debugging techniques for CFC's
I think you have to do isStruct(), isArray, isScalar, etc.
 
Try my dump.cfc, available from cfczone.org
----- Original Message -----
Sent: Saturday, October 18, 2003 1:42 PM
Subject: RE: [CFCDev] Debugging techniques for CFC's

Yep that works�I tossed it in components.cfc which all components extend (in my dev environment only � don�t need in prod)

Some of my variables are complex types i.e. other components�is there a �typeOf� type function available so I could loop through all properties and dump and child objects?

 

Thanks for tip!

 

Stace

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nando
Sent: October 18, 2003 2:23 PM
To: [EMAIL PROTECTED]
Subject: RE: [CFCDev] Debugging techniques for CFC's

 

OK ... so this works pretty well, and you get all the variable and the functions.

 

 <cffunction name="dump" access="public" output="yes">
  <cfdump var='#variables#'>
 </cffunction>

 

I found the script in the archives ... from August 14th, which is roughly a month or so back. :) Now lemme see if i can get it to work.

 

-----Original Message-----
From: Dawson, Michael [mailto:[EMAIL PROTECTED]On Behalf Of Dawson, Michael
Sent: Saturday, October 18, 2003 6:14 PM
To: [EMAIL PROTECTED]
Subject: RE: [CFCDev] Debugging techniques for CFC's

You can put things in the Variables scope.  If you dump the variables scope, you get all variables as well as functions, I believe.

 

I, like Nathan, create a structure named "Instance" that stores all of my data in a cfc.  I can easily dump or output the Instance "scope" and see all that it contains.

 

Also, as an additional comment, a month or so back, I posted an ActionScript for HomeSite or CFStudio that lets you toggle the Yes/No value of the OUTPUT attributes for CFCOMPONENT and CFFUNCTION tags.  This is an easy way of toggling debugging information.

-----Original Message-----
From: Nando [mailto:[EMAIL PROTECTED]
Sent: Sat 10/18/2003 10:03 AM
To: [EMAIL PROTECTED]
Cc:
Subject: RE: [CFCDev] Debugging techniques for CFC's

This may be obvious, but is there a trick to expose the internals of a cfc
to cfdump? I suppose i could use the this scope to develop, and then change
it to variables once it's working correctly. I just find it a little
cumbersome to be changing the scope back and forth, and it opens the
possibility of introducing errors. So i was hoping to avoid using "this".

St�phane, how do you do this?

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of St�phane Bisson
> Sent: Saturday, October 18, 2003 4:15 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [CFCDev] Debugging techniques for CFC's
>
>
> I'm debugging my CFCs using the cfoutput and cfdump... with
> debuggind enable
> in CF admin.... this is the only way I'm debugging my CFCs right
> now... may
> be in futur it will different...
>
> Stephane
> ----- Original Message -----
> From: "Nando" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, October 17, 2003 9:12 PM
> Subject: [CFCDev] Debugging techniques for CFC's
>
>
> > Hi all,
> >
> > I'm finding one of the most challenging aspects of working with CFC's,
> > especially as a novice, is that it's difficult to debug a properly
> > encapsulated object. I've started to wonder what stategies or techniques
> are
> > being used to expose the internals of a cfc when something isn't working
> > right, especially when you're stuck in the middle of a complex function
> > somewhere.
> >
> > Any tips would be highly appreciated after a very long day of struggling
> > through 2 of these.
> >
> >
> >
> > ----------------------------------------------------------
> > You are subscribed to cfcdev. To unsubscribe, send an email
> > to [EMAIL PROTECTED] with the word '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]
> >
>
> ----------------------------------------------------------
> You are subscribed to cfcdev. To unsubscribe, send an email
> to [EMAIL PROTECTED] with the word '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]


----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word '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]



AVIS IMPORTANT:
-------------------------------
Les informations contenues dans le present document et ses pieces jointes sont strictement confidentielles et reservees a l'usage de la (des) personne(s) a qui il est adresse. Si vous n'etes pas le destinataire, soyez avise que toute divulgation, distribution, copie, ou autre utilisation de ces informations est strictement prohibee. Si vous avez recu ce document par erreur, veuillez s'il vous plait communiquer immediatement avec l'expediteur et detruire ce document sans en faire de copie sous quelque forme.

WARNING:
-------------------------------
The information contained in this document and attachments is confidential and intended only for the person(s) named above. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution, or any other use of the information is strictly prohibited. If you have received this document by mistake, please notify the sender immediately and destroy this document and attachments without making any copy of any kind.

Reply via email to