Vince wrote: "Having said this, it should be noted that there are discrepancies between the documentation and actual implementations, and differences between the CF5 and CFMX implementations. Also, there are certain well-known authors who tend to publish CFML examples that are at odds with the documentation, but which happen to work on one or both of the CF5/MX implementations; these examples tend to then assume "pseudo-official" status among the CFML community."
Code examples which work but are "at odds with the documentation" tend to be that way for a reason. Most likely, it may not work in future versions (engineers know a lot about where they are headed in future versions), and if it's not documented as "officially supported" then it may not be included in backwards compatibility engineering. Developers should be very leary of using such code, and if used, at least keep good notes so it can be located during a future migration for debugging/correction. On the other point that "that there are discrepancies between the documentation and actual implementations," I'd have to say that's basically a bug, be it incorrect documentation, or incorrect functioning. Be sure to report anything like this. Thanks! Vernon Viehe ColdFusion Community Manager Developer Relations Macromedia, Inc. Online diary: http://vvmx.blogspot.com/ -------------------- Macromedia DevCon 2002, October 27-30, Orlando, Florida Architecting a New Internet Experience Register today at www.macromedia.com/go/devcon2002 -----Original Message----- From: Vince Bonfanti [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 6:05 AM To: CF-Talk Subject: RE: BlueDragon (was RE: How is CFMX J2EE implemented?) Other than the part about a "parser" (BlueDragon is much more than that), I absolutely agree. Here's New Atlanta's position regarding the CFML "standard": 1) There is only one CFML standard, which is defined by: (a) the "specifications" as represented by Macromedia's published documentation for CF5/CFMX; and, (b) the "reference implementations", that is, CF5/CFMX. (Having said this, it should be noted that there are discrepancies between the documentation and actual implementations, and differences between the CF5 and CFMX implementations. Also, there are certain well-known authors who tend to publish CFML examples that are at odds with the documentation, but which happen to work on one or both of the CF5/MX implementations; these examples tend to then assume "pseudo-official" status among the CFML community. All of this makes life very interesting when trying to implement a "compliant" CFML server). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
