This blog isn't maintained anymore. Check out my current project, an agile/scrum management tool.

Wednesday, August 22, 2007

Mysterious flex compiler error

1119: Access of possibly undefined property someOtherMember through a reference with static type SecondClass ...

Sometimes, the flex compiler just decides to start throwing this error around. It's usually on a line such as:

SomeClass.someMember.someOtherMember = "Hi";

With some simple definitions like...

class SomeClass
{
public static var someMember:SecondClass;
}

class SecondClass
{
public var someOtherMember:String;
}

A clean-build will often make the reported error go away. But sometimes it won't. The error will start happening at seemingly random times when I've been working on completely unrelated sections of the code. One compile everything is fine, then the next it just starts complaining when nothing related was changed.

It happens in FB2, FB3 (using the FB2 SDK), and when compiling from the command line using the FB2 SDK. I haven't seen it using the FB3 SDK, but that doesn't help me since it happens fairly infrequently.

This is a compile-time error, not a run-time error, so it has nothing to do with variables not being initialized. There's no other errors (or even warnings for that matter) in the project.

Labels:

3 Comments:

  • Post a bug:
    http://bugs.adobe.com/flex/

    By Blogger maliboo, At 8/22/2007 5:43 AM  

  • I just got this as well. Flex Builder 3 (Version 3.0, build 3.0.2.214193).

    Commenting out the offending lines, compling, then uncommenting fixed the issue... fortunately. Stupid compiler!

    By Anonymous Anonymous, At 5/21/2010 8:59 PM  

  • Did you manage to permanently resolve this problem? Fiddling around with commenting and uncommenting lines doesn't work for me, because the project is compiled using an integration server and it always compiles from scratch...

    By Blogger Unknown, At 4/27/2011 5:26 AM  

Post a Comment

Subscribe to Post Comments [Atom]



<< Home