> In this case Adobe Coldfusion brakes the rules of the Adobe Coldfusion > documentation and Railo does not, so what is the correct behaviour in > this case?
understood ... but is this: (a) a bug in Adobe's runtime (b) a bug in Adobe's documentation As someone that has followed their documentation and implementation very closely for near on 10 years now, i can tell you that you can pretty much forget about what the documentation claims it should do, and only observe what actually happens. The documentation, sadly, is only a ROUGH guideline :) I personally believe Adobe would have the hardest job adhering to any official standard, because their engine is littered with lots of cases that leave you scratching your head. Adobe aren't going to break these cases just to be compliant with open source engines that are effectively taking revenue away from their product. So in principal I agree that a standards document would be a wonderful thing to refer to. But in reality I don't believe the majority of CFML developers really care, and will quite happily stick with their engine of choice and whatever one they feel makes them more productive and financially more secure. We as engine developers, are always listening to what you guys want, and as you can probably see, we are quick to react and deliver what you need. I believe the community, YOU, are the ultimate the standards committee. --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
