> Objects still support undefined and null

No; type Object can store null but not undefined. Only an untyped var (indicated by foo:*) can store undefined.

- Gordon


-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tim Hoff
Sent: Monday, May 22, 2006 4:48 PM
To: [email protected]
Subject: [flexcoders] Re: 1.5 migration: How are you handling the loss of undefined and null states for vars?

Objects still support undefined and null.  Can you think of a way to
bind objects to your boolean variables (like an associative array
hashmap)?

-TH

--- In [email protected], "Tracy Spratt" <[EMAIL PROTECTED]>
wrote:
>
> This has definitely become my biggest issue.  I have been
depending on
> checking for uninitialized variables containing undefined or null,
but
> in 2.o this is no longer possible.
>
> I can see coming up with some values that are very unlikely to be
> duplicated as initial values for string and numbers, but boolean
> variables are a bigger problem.
>
> I guess  will have to create a flag variable for each boolean and
set
> its value when the main variable is first modified, then check it
to
> determine the intialize status when needed.
>
> Does anyone have any clever approaches to this?
>
> Tracy
>







--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links









--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to