Me too. I originally intended them to be a structure and it was an oversight that we didn't put <cfset XFA = StructNew()> into the core file. I think, though, that this may cause problems for J2EE version of FB. I'll check with the folks at Synthis on this.
-----Original Message----- From: John Farrar [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 30, 2002 12:18 PM To: [EMAIL PROTECTED] Subject: RE: FB3, CF MX and fuseaction variable I like the idea of all the xfa's being grouped into a structure block. John >>> [EMAIL PROTECTED] 04/30/02 10:46AM >>> XFA's may be a problem since since they are, by convention, local variable with a dot in their name [XFA.ExitName]. Of course, they could easily be renamed as [XFA_ExitName]. When running your FB app in MX, just do a global search and replace for "XFA." and replace it with "XFA_" At 09:24 AM 4/30/02 -0400, hal helms wrote: >Variable *names* with dots in them are the problem. In FB's case, it's >not the names but the values which have dots and that's perfectly fine. > >-----Original Message----- >From: a moustapha [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, April 30, 2002 8:48 AM >To: [EMAIL PROTECTED] >Subject: FB3, CF MX and fuseaction variable > > >I have read in the cfmx_dev_cf_apps.pdf (page 49) that variables with >points in it are not alowed anymore in CF MX(unless using an array >structure p.51). > >As fuseaction is such a variable, I think fb3 will not work on MX. Am I >wrong? Is there going to be a FB3MX version that deals with this issue? > >I won't be using CF MX any time soon, unless my provider makes the >switch, but I want to be prepared. > >p.49: >With the exception of Cookie and Client scope variables (which must >always be simple variable types), you cannot normally include periods >in > >simple variable names. However, ColdFusion makes some exceptions that >accommodate legacy and third-party code that does not conform to this >requirement. > >p.51: >You can create a variable name that includes periods by using >associative array structure notation, as described in "Structure >notation," in Chapter 5. To do so, you must do the >following: >.Refer to the variable as part of a structure. You can always do this, >because >ColdFusion considers all scopes to be structures. For more information >on scopes, see >"About scopes" on page 58 >.Put the variable name that must include a period inside square brackets > >and single or >double quotation marks, >The following example shows this technique: ><cfset Variables ['My.Variable.With.Periods'] =12> ><cfset Request ["Another.Variable.With.Periods"] ="Test variable"> ><cfoutput> My.Variable.With.Periods is:#My.Variable.With.Periods#<br> >Request.Another.Variable.With.Periods is: >#Request.Another.Variable.With.Periods#<br> ></cfoutput> > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
