> 19: <cflock scope="server" type="readonly" timeout="30">
> 20: <cfset intColdFusionVersion =
> listFirst(server.coldfusion.productversion)>
> 21: </cflock>
> 22:
> 23: <cfif intColdFusionVersion eq 5>
> 24: <cfdump var="#arrTest1#">
> 25: <hr>
> 26: <cfdump var="#arrTest2#">
> 27: <cfelse>
> 28: <cfoutput>
An off topic comment on the code block above. Doing code like this,
where you have a code branch for CF5 and a code branch for <5, will
result in an error if you turn on strict attribute validation. We ran
across this in a Spectra template and had to move the CF5 code into an
include. Like so:
<CFIF CF5>
<CFINCLUDE ...>
<CFELSE>
old code
</CFIF>
Just something to watch out for.
=======================================================================
Raymond Camden, Principal Spectra Compliance Engineer for Macromedia
Email : [EMAIL PROTECTED]
Yahoo IM : morpheus
"My ally is the Force, and a powerful ally it is." - Yoda
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
