One thing that’s worth noting as an exception to that is when you need to keep accessors present for the sake of implementing interfaces. Basically one could think of this as “enforcing” a public member’s presence just by providing accessors to it, because you can’t enforce members in interfaces and AS3 has no abstract keyword.

Eg. my IEntity interface require mapX and mapY get and set accessors, otherwise game logic cannot position entities in the world. Although they do nothing more than a simple public variable mapX or mapY would, they are required in order to adhere to the interface specification for “what makes an entity”.

Your coding conventions are great, they’re pretty much exactly the same as mine, with the exception of m_, I use _ instead, and __ (double underscore) for incoming arguments.

The only thing I see a problem with is this: “Class Members Class member variables are prefixed with “m_” and must always be private. m_remainingLives m_moneyInAccount”

I used to share this opinion but in all truth, if a member variable is accessible via accessors with no additional logic other than set/return in those accessors, why bother to create a separate get and set for it? All you’re doing is creating work for yourself. If the var is properly public (read/write) then just set it public and don’t give it a prefix. Otherwise it’s just pointless code clutter.