It isn't up to Adobe to define how the Date class works. The Player team's intention is to follow the Ecma-262 spec for this class. I haven't checked what the spec has to say about this, but if the Player isn't in compliance, that's a bug.
Gordon Smith Adobe Flex SDK Team ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Harui Sent: Saturday, May 17, 2008 8:50 PM To: [email protected] Subject: RE: [flexcoders] Re: bug in setMonth() method? Yes. In Flex we have a GIGO policy. "garbage in, garbage out". We have enough complaints about runtime memory usage, swf size and performance that adding parameter checking was not practical. The player does some checking, but not everywhere as well for the same reason. That said, we hope to have time to use conditional compilation to put in more dev-time checking in future releases, but if we do, I don't want to hear complaints about why the debug version is so slow. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Amy Sent: Saturday, May 17, 2008 7:38 AM To: [email protected] Subject: [flexcoders] Re: bug in setMonth() method? --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > I would not guarantee results if you set values that are out of range. So you think that it's ok to fail silently and return a nearly appropriate value rather than throwing an error?
