Comments on: From C++ to ActionScript 2.0, 4: Abstract Classes http://nodename.com/blog/2005/09/19/abstract-classes/ Fri, 02 Jul 2010 12:12:19 -0600 hourly 1 http://wordpress.org/?v=3.0 By: Andrew Paul Simmons http://nodename.com/blog/2005/09/19/abstract-classes/comment-page-1/#comment-27264 Andrew Paul Simmons Thu, 07 Jun 2007 16:26:38 +0000 http://nodename.com/blog/?p=8#comment-27264 I am glad you found my article useful. I am glad you found my article useful.

]]> By: Alex Bradley http://nodename.com/blog/2005/09/19/abstract-classes/comment-page-1/#comment-27 Alex Bradley Tue, 20 Sep 2005 15:42:54 +0000 http://nodename.com/blog/?p=8#comment-27 Hi Alan, We've implemented abstract classes in the KineticFusion AS2.0 compiler using class metadata defined within Javadoc comments. This ensures that abstract classes cannot be instantiated, and that classes can partially implement interfaces safely. There are two primary kinds of abstract classes - those that partially implement interfaces and abstract base classes intended only for extension. To ensure cross-compiler compatibility, all abstract members are defined with empty class member stubs - these are removed automatically by the compiler and the compiler then fully checks both constructor access and the parent hierarchy to ensure that all declared abstract members and missing interface methods are implemented in the concrete class. It would be really great if you could have a look at our implementation and let us know your comments. We've also added metadata for 'final' and 'const' keywords as well as suppport for multiple valid signatures for class methods. Cheers, Alex Hi Alan,

We’ve implemented abstract classes in the KineticFusion AS2.0 compiler using class metadata defined within Javadoc comments. This ensures that abstract classes cannot be instantiated, and that classes can partially implement interfaces safely.

There are two primary kinds of abstract classes – those that partially implement interfaces and abstract base classes intended only for extension. To ensure cross-compiler compatibility, all abstract members are defined with empty class member stubs – these are removed automatically by the compiler and the compiler then fully checks both constructor access and the parent hierarchy to ensure that all declared abstract members and missing interface methods are implemented in the concrete class.

It would be really great if you could have a look at our implementation and let us know your comments. We’ve also added metadata for ‘final’ and ‘const’ keywords as well as suppport for multiple valid signatures for class methods.

Cheers,

Alex

]]>