The problem is that 'string' is way too lenient, because you want to allow dates, the empty string and that's it. A type of 'string' will also allow "hulabaloo" to be passed without error, which is undesirable. Of course, you HAVE to use type="string" in order to circumvent CF's weird type system, but by doing so, you're basically removing the utility of having the typing system at all (and may as well just leave the attribute off). Not that I recommend that, but it's frustrating to have to jump through silly hoops like this in a language that primary design characteristic is ease of use.
cheers, barneyb On 9/20/05, Patrick McElhaney <[EMAIL PROTECTED]> wrote: > On 9/20/05, Peter Hardy <[EMAIL PROTECTED]> wrote: > > I've created a transfer object that takes amongst others a couple of date > > parameters. Trouble is, they are optional parameters so sometimes they are a > > valid date and sometimes they are equal to "". If my cfargument type to date > > cf just throws an exception. > > Sometimes it's a valid date, but it's always a valid string, right? > Wouldn't it be appropriate to make the argument type string? > > Patrick > > > -- > Patrick McElhaney > 704.560.9117 > http://pmcelhaney.weblogs.us > > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ---------------------------------------------------------- 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]
