Comments on: Understanding AS3 super() statement

By: Muhammad bin Yusrat

Muhammad bin Yusrat — Tue, 06 Dec 2011 18:03:30 +0000

This is without a doubt the most easy to understand explanation of Super() for AS3 on the internet.

Hats of to you broh!

Thanks!

By: vxcriss

vxcriss — Sat, 13 Aug 2011 21:39:59 +0000

Very nice explanation and to the point, thanks. I just spent 15 minutes trying to figure out how this is called cause it wasn’t working with parent as it does in PHP :)

By: Fernando Silva

Fernando Silva — Wed, 29 Jun 2011 13:52:55 +0000

Thanks a lot for this knowledgement!

By: Xavier

Xavier — Sun, 21 Feb 2010 13:04:36 +0000

“So in this case I could remove the import flash.display.Sprite; line. ”

you can remove it only if you dont use Sprite class inside.

adding this var s:Sprite=new Sprite(); somewhere and removing import gives an error. Actually thats what i dont understand.

By: ViolentAJ

ViolentAJ — Tue, 11 Aug 2009 19:21:53 +0000

Also, don’t forget that if the super-class’s constructor had arguments, that you can call super(arg0, arg1, … argX), and you would HAVE to if the super’s constructor had arguments.

By: Josh

Josh — Tue, 11 Aug 2009 05:11:21 +0000

I understand the super() command, but I always wondered why I would use it.

By: Andrew Jacobs

Andrew Jacobs — Mon, 10 Aug 2009 20:06:40 +0000

Now that you mention it, it would be great to see a superclass that uses constructor parameters which follow the Strategy pattern. That way you could derive subclasses from in-game Sprites and assign them different behaviors by passing in things like a “AIStrategy” or a “PhysicsStrategy”.

Thanks for the post, Emanuele.

By: Dan

Dan — Mon, 10 Aug 2009 20:03:49 +0000

Hey,

Actually the textbook opinion is prefer composition over inheritance.
Well, I never really understood why so I used inheritance frequently. Cause I thought just like you hey nice, I put common stuff in the parent and add custom stuff to the child class.
After I while though I realized it often costs me time .. jumping back and forth between parent and child classes to make sure things happen as intended.

I guess it’s because it increases my ‘mental workload’. With composition I only have to worry about a class’ public API -while with composition I have to worry about the whole class!
So nowadays I use inheritance only when it absolutely makes sense, like when a child class is really a variation of the parent class, not just borrowing some functionality.
For some reason I feel more relaxed nowadays. ;-)

Ciao, Dan