I would think only if the data that is associated with the boolean
variable is null or not.

Tim

--- In flexcoders@yahoogroups.com, "Tracy Spratt" <[EMAIL PROTECTED]>
wrote:
>
> I see that doc.  I have been working off the Migration Guide pdf,
which
> seems a bit out of date.
>
> Yes, Object was the way I decided to go.  Definitely cleaner than
> creating flag variables.
>
> I wonder if I will need to cast the object to a boolean to compare?
>
> Tracy
>
> -----Original Message-----
> From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On
> Behalf Of Tim Hoff
> Sent: Tuesday, May 23, 2006 6:10 PM
> To: flexcoders@yahoogroups.com
> Subject: [flexcoders] Re: ? Variables of type Object can not be
> undefined. undefined will be type coerced to Object before
comparison.
>
> Tracy,
>
> Good reference under Special Types.  But, wouldn't this work in
your
> situation?
>
> var bValid:Object;
> if (bValid == null)
>
> Tim
>
> --- In flexcoders@yahoogroups.com, "Darren Houle" <lokka_@> wrote:
> >
> > In the API docs it says about "undefined"
> >
> > public const undefined:*
> >
> > A special value that applies to untyped variables or dynamic
> object
> > properties that have not been initialized. The value undefined
> applies to
> > untyped variables that have not been initialized. In
ActionScript
> 3.0 only
> > variables that are untyped can hold the value undefined, which
is
> not true
> > in ActionScript 1.0 and ActionScript 2.0. For example, both of
the
> following
> > variables are undefined because they are untyped and unitialized:
> >
> > var foo;
> > var bar:*;
> >
> > So I just assumed "undefined" was only for use with untyped
and/or
> > unitialized dynamic vars.  There's nothing here about typing as
> Object. 
> > Maybe the docs have conflicting information in different places
> since the
> > recent change to undefined???
> >
> > Darren
> >
> >
> >
> >
> > >From: "Tracy Spratt" <tspratt@>
> > >Reply-To: flexcoders@yahoogroups.com
> > >To: <flexcoders@yahoogroups.com>
> > >Subject: [flexcoders] ? Variables of type Object can not be
> undefined. 
> > >undefined will be type coerced to Object before comparison.
> > >Date: Tue, 23 May 2006 17:35:42 -0400
> > >
> > >Why is the compiler is giving me this error when I do a
> comparison:
> > >var bValid:Object;
> > >if (bValid == undefined) ...
> > >
> > >Even though the docs state:
> > >In ActionScript 3.0, undefined is only for use with type Object.
> > >
> > >The doc is the latest Migration Guide pdf.
> > >
> > >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