PureMVC Architects Lounge

Hi there,

I've got a suggestion for the usage of the "as" casting in the as3 port. It's not really useful to do so. It makes it worst to debug the code.

Using this:

var userProxy:UserProxy = facade.retrieveProxy(UserProxy.NAME) as UserProxy;

and getting a NULL return of any reason will effect your code at another position in the code. That makes it harder to debug while the debugger jumps to the wrong position in the Code.


I would rather recommend using this:

var userProxy:UserProxy = UserProxy(facade.retrieveProxy(UserProxy.NAME));

then the player is immediately throwing an exception at the right position in the stack and not when the userProxy is used later in the code.


Cheers

Certainly a good point. It's not an issue usually if you've already registered your Proxies at startup, as most PureMVC apps do.

-=Cliff>

Just in Case of code improvment. Last project we had Somerset issues with piping where I followed the paradigm ;) good insane while debugging. Sometimes you don't think about those compiler stuff


Flo 

Performance wise "Class()" casting is a lot faster then "as Class". Are you planning to change that in the next rlz?

There are only two places in the entire Standard version framework where an 'as Class' cast is used, and that is in the View.notifyObservers and View.removeObserver methods. In both cases, they are getting the observer list for a given notification like this:

 var observers:Array = observerMap[ notificationName ] as Array;
Since the execution of these calls only happens once in the method (the real work is subsequently visiting each of the observers in the list), I don't see a reason to optimize it. UPDATE: Actually, it can't be changed, as Array and Date are the two types that must be cast with 'as'. For arrays, a call to Array(xxx) will create an Array with one element: xxx.

Really, the best practices need to change in programs using PureMVC. And I've already taken a step in that direction. Just the other day I updated the Flex EmployeeAdmin demo to reflect best practices, and I made all the casts of retrieved Proxies and such use the 'Class()' casting instead of 'as Class'.

-=Cliff>

Really, the best practices need to change in programs using PureMVC. And I've already taken a step in that direction. Just the other day I updated the Flex EmployeeAdmin demo to reflect best practices, and I made all the casts of retrieved Proxies and such use the 'Class()' casting instead of 'as Class'.

I'm really glad to hear that!  A lot of programmers on my team have been using "as" for regular casting now because they saw it in some PureMVC demo or another and I've been having to convince them that regular casting is correct despite whatever online tutorials they may have seen.  You pull a lot of weight!

Useful reference on this topic:
http://stackoverflow.com/questions/996478/actionscript-is-there-ever-a-good-reason-to-use-as-casting (http://stackoverflow.com/questions/996478/actionscript-is-there-ever-a-good-reason-to-use-as-casting)