Thank you Andy! That back-story is helpful in understanding what otherwise just seemed just plain weird - from the standpoint of a typical ColdFusion affectionado.
So apparently, the BD commercial product was never originally designed with CF compatibility as a "prime directive", so to speak. Almost like "middleware" or "transitionware" to bridge platforms perhaps? Now that more and more economically-challenged former CF developers are trying OpenBD as an entry or conversion point; compatibility issues are more important there, and are hopefully being addressed in squeaky wheel methodology? Alan K. Holden Andy Wu wrote: > To answer your question Alan, it was implemented with compatibility > between our own products BlueDragon and BlueDragon.NET as the priority > over compatibility with CF. That was a business decision made by New > Atlanta and since open sourcing BlueDragon, the implementation hasn't > changed. (snip) --~--~---------~--~----~------------~-------~--~----~ 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 !! -~----------~----~----~----~------~----~------~--~---
