Comments on: Learn some patterns – Advanced ActionScript 3.0 with Design Patterns http://blog.hexagonstar.com/learn-some-patterns-advanced-actionscript-30-with-design-patterns/ "Chaotic Neutral" Fri, 30 Jul 2010 17:50:37 +0000 hourly 1 http://wordpress.org/?v=abc By: Jan Breens http://blog.hexagonstar.com/learn-some-patterns-advanced-actionscript-30-with-design-patterns/comment-page-1/#comment-531 Jan Breens Fri, 19 Jan 2007 16:00:36 +0000 http://blog.hexagonstar.com/learn-some-patterns-advanced-actionscript-30-with-design-patterns/#comment-531 I've just bought this book, and coming from a JAVA & .NET background some years ago, it's nice to see AS books finally going in the direction I am used to reading. It was comforting to read a nicely written, easy to understand book. As you say, there are some slips, but I consider that normal. AS3.0 is really new, and I'm glad they didn't go for the "safe thing" but tried to do something new in the world of Flash & AS books. Nice book with an equally nice review. I’ve just bought this book, and coming from a JAVA & .NET background some years ago, it’s nice to see AS books finally going in the direction I am used to reading.

It was comforting to read a nicely written, easy to understand book. As you say, there are some slips, but I consider that normal. AS3.0 is really new, and I’m glad they didn’t go for the “safe thing” but tried to do something new in the world of Flash & AS books.

Nice book with an equally nice review.

]]> By: Waterproof AS 3.0 Singleton at H1DD3N.R350URC3 http://blog.hexagonstar.com/learn-some-patterns-advanced-actionscript-30-with-design-patterns/comment-page-1/#comment-530 Waterproof AS 3.0 Singleton at H1DD3N.R350URC3 Fri, 24 Nov 2006 14:22:55 +0000 http://blog.hexagonstar.com/learn-some-patterns-advanced-actionscript-30-with-design-patterns/#comment-530 [...] While reading Advanced ActionScript 3 with Design Patterns I’ve once again came across the AS 3.0 Singleton solution that has to deal with the absence of private constructors (I’ll save my rage and cursings about who had the idea to remove them for now ) and while the authors are using the already well known method of using a SingletonEnforcer class outside the Singleton’s package to verify that the class cannot be  instanciated via the constructor they also note that this can be doublecrossed by giving null or undefined as a constructor parameter. As this is rather sub optimal I was wondering why they don’t just check inside the Singleton constructor for a null/undefined argument and throw an exception accordingly?!I’m sure somebody else had the same idea already but here’s my idea of a waterproof Singleton class that cannot be misused from the outside (As always, if I missed any detail that accidentally breaks hell loose feel free to correct me) … [...] [...] While reading Advanced ActionScript 3 with Design Patterns I’ve once again came across the AS 3.0 Singleton solution that has to deal with the absence of private constructors (I’ll save my rage and cursings about who had the idea to remove them for now ) and while the authors are using the already well known method of using a SingletonEnforcer class outside the Singleton’s package to verify that the class cannot be  instanciated via the constructor they also note that this can be doublecrossed by giving null or undefined as a constructor parameter. As this is rather sub optimal I was wondering why they don’t just check inside the Singleton constructor for a null/undefined argument and throw an exception accordingly?!I’m sure somebody else had the same idea already but here’s my idea of a waterproof Singleton class that cannot be misused from the outside (As always, if I missed any detail that accidentally breaks hell loose feel free to correct me) … [...]

]]>