Wouldn't it be great to have a "CFML Standards" committee to whom you could propose these sorts of questions and get an official, definitive, documented answer about how it should work? That way you could "code to the spec" and be confident that it would work consistently across vendor implementations and not change arbitrarily in the future?
I know at least one CFML vendor who would be happy to support, sponsor, and/or participate in such a committee, and heed their decisions... :-) Vince > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Milligan > Sent: Thursday, March 18, 2004 6:25 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] Unscoped references in CFSET within CFFUNCTION > > > Yeah, > > I guess I'll just have to make sure I'm on any future betas > and submit a bug if they do decide to change the way it works ;) > > Spike > > >-----Original Message----- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] On Behalf Of Paul Kenney > >Sent: Thursday, March 18, 2004 3:13 PM > >To: [EMAIL PROTECTED] > >Subject: RE: [CFCDev] Unscoped references in CFSET within CFFUNCTION > > > >Spike, > > > >I would be weary of doing that though... Like you said, who > >knows why they did it that way -- and who knows when or why > >they might change their mind. > >Kind of cool though. > > > >Paul Kenney > >WebMaster, CorporateWarriors.com > >916-663-1963 > > > > ---------------------------------------------------------- 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]
