Sean Corfield wrote: > Sounds like OpenBD is somehow treating the null-value return / > assignment as storing an empty string in the variable - which is > certainly not the correct behavior
Only if you define "correct" as "whatever Adobe CF does." <cfset foo = null /> shouldn't make anything "disappear." That's just plain dumb, and certainly shows that CFML doesn't handle nulls logically. Null doesn't mean something doesn't exist, it just means it doesn't have a defined value, and the closest thing in CFML is a zero-length string, so from where I stand OpenBD is handling it exactly as it should. I can't imagine why you'd want a null value to be treated as something that doesn't even exist. This is also an edge case--I don't think you're going to see much CFML code at all that uses null in this way, and given that null isn't even a real concept in CFML, it seems a odd to have code that relies on it in my opinion. --~--~---------~--~----~------------~-------~--~----~ 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 !! -~----------~----~----~----~------~----~------~--~---
