You never want to references environment variables from within a CFC. CFCs have their own environment (the 'this' scope and the unnamed scope) which they should be constrained to. The CF processing engine doesn't enforce this right now, but you as a developer should.
--- Barney Boisvert, Senior Development Engineer AudienceCentral [EMAIL PROTECTED] voice : 360.756.8080 x12 fax : 360.647.5351 www.audiencecentral.com > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Matthew Walker > Sent: Thursday, July 31, 2003 5:02 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] envronment variables and CFCs > > > > Option 3 I think would limit possible > > inheritance needs in the future (but I might be wrong > > This is re all CFCs inheriting from some core CFC that knows about > environment variables... > > Well I guess it wouldn't if you insisted that the CFC you inherit from > inherits from that core CFC. i.e. the rule would be all CFCs > either inherit > from your core CFC or some other CFC. > > > > ---------------------------------------------------------- > 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). > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.504 / Virus Database: 302 - Release Date: 7/24/2003 ---------------------------------------------------------- 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).
