On 3/11/14 11:42 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> But at runtime the actual code that runs is written in C. And that's >>why >> every Flex SWF I know of can be compiled with playerglobal.swc in the >> external library path. No code from playerglobal.swc gets linked in to >> the SWF yet those SWFs run fine. > >That may be the case and sorry again for getting this off topic but it is >rather curious. > >Can you explain why there is ActionScript class and methods not marked as >native in playerglobal.as? Here's one exmaple. [1] It could be that "native" isn't required anymore and everyone needs to externally link. Don't know for sure. My understanding is that the public APIs need to be there because the compiler parses the library.swf to build up the class definitions the compiler will use when compiling your app. You can see from [1] that most methods are stubs. I have no idea why some methods have bodies or why there are private methods. It might also be used internally for test generation. I don't think there is a way to override a built-in player class. The ApplicationDomain rules would cause me to expect that all classes in playerglobal.swc are already in the ApplicationDomain before your SWF loads and first-in wins. -Alex > >1.http://stackoverflow.com/questions/6046685/is-it-possible-to-read-and-ma >ybe-change-the-sources-of-the-core-flash-class-fi
