On 5/13/05, Barney Boisvert <[EMAIL PROTECTED]> wrote: > isNumeric should test whether a given value is a number. It's > debatable whether it should test whether a given value is both not > null and a number, but CFML is such that it doesn't matter. > Personally, I'd say that isX functions should return false for null > values.
Since isObject() is how you normally test whether something is a component and null would be any component type, you could easily argue that isObject(null) should be true... Like I say, this is all about language semantics and that's a wonderfully rich and tricky area for language lawyers (who, unfortunately, are the people who need to define what the language does). > If I have an integer column in a database, I damn well better never > get a string back from querying it. Ick. Give me a number or null > (which is a 'nothing' of every type, including number). Yes, although that's not how CF behaves today since it does not return NULL from a DB query. > If I'm testing user input, it is impossible to get anything except > strings. Well, that depends. You could have conditional fields so you might have 'null' field values (or at least not structKeyExists(form,'something') which today is the same as null). Again, my point is that null is a fuzzy concept in CF today. -- Sean A Corfield -- http://corfield.org/ Team Fusebox -- http://fusebox.org/ Got Gmail? -- I have 50, yes 50, invites to give away! "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
