If all of the getters and setters in Moai's entire codebase were generated using macros, I'd probably agree.  My objection to the macro is that we're introducing a new convention.  Let's say that I'm unfamiliar with this class, and I run into a problem with it.  If it's implemented the same way that all of the other classes are implemented in Moai, then I'll know exactly where to look to fix the problem.  :mag_right:   If it's implemented with macros that are specific to this one class, I won't be able to search for the function to know where to find it.  If I do manage to find it, I'll have to figure out what the macros are doing and decode them before I can get to work.  I may even have to remove the macro and replace it with a regular function first.  :unamused: 

The other issue with these macros is that they mess up documentation.  :notebook_with_decorative_cover:   Moai has a standard format for auto-generating docs, and this makes it impossible.  It's particularly important to explain what each of these properties affects in the particle system, and there's no way to do that if they're all lumped into a ```setProperty``` method.  :camel: