Comments on: Polymorphism in ActionScript 3.0

By: Jorge Pereira

Jorge Pereira — Tue, 21 Apr 2009 05:54:27 +0000

To El above,

Initially I thought typecasting: A(m).abc()

But in any case, if you find yourself needing to do it often, then it’s time to revise your code

By: RaymonWazerri

RaymonWazerri — Fri, 20 Apr 2007 23:42:06 +0000

Hey,
I love what you’e doing!
Don’t ever change and best of luck.

Raymon W.

By: El

El — Wed, 24 Jan 2007 00:12:47 +0000

Actually, a question:

Class A – a super class with method abc();
Class B – a subclass of A that has overridden abc() method;

var m:A = new B();

m.abc() => calls abc() from class B;

How do I call abc() from class A (syntax)?
(i’ve tried e.g., m.super.abc() which didn’t work)

Regards,

By: Philip

Philip — Tue, 10 Jan 2006 16:48:32 +0000

It looks like c# besides no
virtual keyword is included

i think there aren’t more changes for new language version …

By: Peter

Peter — Mon, 02 Jan 2006 05:12:27 +0000

when using polymorphism through inheritance you came across that problem in AS2.0 of not having an ability to protect your methods from being overridden.

I always preferred to use interfaces to enforce polymorphism whenever possible.

By: Tony MacDonell

Tony MacDonell — Mon, 02 Jan 2006 04:11:06 +0000

Actually, Polymorphism goes far beyond Inhertiance and overriding methods these days.

The truest expression of it in Actionscript 3 (and 2 as well) is the usage of interfaces, and usage of interfaces as a data type.

Actionscript 3 actually allows you to type a variable to an Interface. You see this frequently used in the new Flex Framework. By typing a var to an interface, you can easily escape from inheritance pitfalls while maintaining the benefits of polymorphism.