Comments on: AS3 — on the lack of private and protected constructors http://kuwamoto.org/2006/04/05/as3-on-the-lack-of-private-and-protected-constructors/ music, technology, interfaces Sun, 29 Jan 2012 05:22:45 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Enric http://kuwamoto.org/2006/04/05/as3-on-the-lack-of-private-and-protected-constructors/comment-page-1/#comment-72169 Enric Sat, 13 Oct 2007 21:15:14 +0000 http://kuwamoto.org/?p=54#comment-72169 As far as I can see there's no generalized method to clean-up when a application terminates. I have a javascript utility that dymanicaly creates media embeds into a DIV (or other HTML container). But on Opera the NetStream isn't closed after the first dynamic embed on the page. So the flash video doesn't play. Why are destructors missing? Is this the design of ECMAScript edition 4? Thanks, Enric As far as I can see there’s no generalized method to clean-up when a application terminates. I have a javascript utility that dymanicaly creates media embeds into a DIV (or other HTML container). But on Opera the NetStream isn’t closed after the first dynamic embed on the page. So the flash video doesn’t play. Why are destructors missing? Is this the design of ECMAScript edition 4?

Thanks,

Enric

]]> By: Juank http://kuwamoto.org/2006/04/05/as3-on-the-lack-of-private-and-protected-constructors/comment-page-1/#comment-64499 Juank Wed, 03 Oct 2007 01:33:37 +0000 http://kuwamoto.org/?p=54#comment-64499 I also wonder if you will also consider Destructor methods and/or operator overloading. I also wonder if you will also consider Destructor methods and/or operator overloading.

]]> By: sho http://kuwamoto.org/2006/04/05/as3-on-the-lack-of-private-and-protected-constructors/comment-page-1/#comment-2366 sho Tue, 25 Jul 2006 22:26:56 +0000 http://kuwamoto.org/?p=54#comment-2366 You know, I don't 100% remember what the discussion around method overloading. I recognize that it's a useful feature, and we decided not to tackle it in ActionScript 3, presumably because of time. I think the reason the lack of private constructors raised such a fuss is that unlike method overloading, this is a feature that was previously available in ActionScript 2. You know, I don’t 100% remember what the discussion around method overloading. I recognize that it’s a useful feature, and we decided not to tackle it in ActionScript 3, presumably because of time.

I think the reason the lack of private constructors raised such a fuss is that unlike method overloading, this is a feature that was previously available in ActionScript 2.

]]> By: Joost Nuijten http://kuwamoto.org/2006/04/05/as3-on-the-lack-of-private-and-protected-constructors/comment-page-1/#comment-2365 Joost Nuijten Tue, 25 Jul 2006 22:22:33 +0000 http://kuwamoto.org/?p=54#comment-2365 Maybe I missed this one, but what happened to 'method overloading' ? Maybe I missed this one, but what happened to ‘method overloading’ ?

]]> By: Jason Nussbaum http://kuwamoto.org/2006/04/05/as3-on-the-lack-of-private-and-protected-constructors/comment-page-1/#comment-239 Jason Nussbaum Thu, 06 Apr 2006 06:37:51 +0000 http://kuwamoto.org/?p=54#comment-239 Thanks for the clarification...I'm also glad to hear it's only 'postponed' for the time being. I ranted about this way back when I first noticed it... Thanks for the clarification…I’m also glad to hear it’s only ‘postponed’ for the time being. I ranted about this way back when I first noticed it…

]]> By: Sho http://kuwamoto.org/2006/04/05/as3-on-the-lack-of-private-and-protected-constructors/comment-page-1/#comment-238 Sho Wed, 05 Apr 2006 18:58:44 +0000 http://kuwamoto.org/?p=54#comment-238 Enum and abstract are definitely things I could imagine being added to the language at some point. I don't know if they are on the radar at present. I'll ask about whether the spec could be published in its current draft form. As for Class.newInstance(args), that's a good suggestion. Thanks! Enum and abstract are definitely things I could imagine being added to the language at some point. I don’t know if they are on the radar at present.

I’ll ask about whether the spec could be published in its current draft form.

As for Class.newInstance(args), that’s a good suggestion. Thanks!

]]> By: Jens Halm http://kuwamoto.org/2006/04/05/as3-on-the-lack-of-private-and-protected-constructors/comment-page-1/#comment-237 Jens Halm Wed, 05 Apr 2006 18:06:20 +0000 http://kuwamoto.org/?p=54#comment-237 Glad to hear that protected and private constructors are just postponed. I really thought this was a limitation Adobe considered as a feature. At least I can now stop publicly whining about it. ;) And yes, they are not that important for enums. I miss them more for abstract classes and always thought that, for example, DisplayObjects constructor throwing runtime exceptions is not an elegant solution since this should be detected at compile time. Btw. since enum and abstract are reserved keywords, is there a chance we see those features in AS 4 or is this something the spec group is currently not working on? And are there any drafts of the spec publicly available? If I google for it, all I can find are drafts that are at least three years old. And one more small thing I would like to see added to the spec in the future is a method like: Class.newInstance(args:Array):Object which would be kind of Function.apply for constructors. I know the workarounds using special initialization methods, but they might not be feasible for existing classes. In AS 2 it was easy to hack around this limitation using the __proto__ property. There were already several postings on Flexcoders for this issue, so I think I'm not the only developer missing this feature. But I don't want to come across too picky. ;-) AS 3 and especially the new Display API is a great step forward. Glad to hear that protected and private constructors are just postponed. I really thought this was a limitation Adobe considered as a feature. At least I can now stop publicly whining about it. ;)

And yes, they are not that important for enums. I miss them more for abstract classes and always thought that, for example, DisplayObjects constructor throwing runtime exceptions is not an elegant solution since this should be detected at compile time.

Btw. since enum and abstract are reserved keywords, is there a chance we see those features in AS 4 or is this something the spec group is currently not working on? And are there any drafts of the spec publicly available? If I google for it, all I can find are drafts that are at least three years old.

And one more small thing I would like to see added to the spec in the future is a method like:

Class.newInstance(args:Array):Object

which would be kind of Function.apply for constructors. I know the workarounds using special initialization methods, but they might not be feasible for existing classes. In AS 2 it was easy to hack around this limitation using the __proto__ property. There were already several postings on Flexcoders for this issue, so I think I’m not the only developer missing this feature.

But I don’t want to come across too picky. ;-) AS 3 and especially the new Display API is a great step forward.

]]>