Stefan Andersson wrote: > One of the biggest impacts on code is the transition from "m_" to explicit > "this." and that commenting, regions and line break formatting is strictly > governed. > > > > As you all know, I've been a proponent of "m_" but that's something I'm > ready to lay aside to achieve consistent code style. I also know that there > is reflecting code depending on the "m_" naming, but those projects can be > excluded until we can get a fix for that. > > > > As StyleCop is implemented as a Visual Studio plug-in I guess code cleanup > will have to be a voluntary effort by the Visual Studio developers. This > proposal is more about embracing the StyleCop code style in itself.
+1 to conforming style here, honestly any set of consistant rules is
better than non consistancy, and if a tool from the windows side of the
house can keep us honest, more power to it.
I personally never liked the m_ anyway, so it going to more explicit
nature would be fine with me.
-Sean
--
__________________________________________________________________
Sean Dague Mid-Hudson Valley
[email protected] Linux Users Group
http://dague.net http://mhvlug.org
There is no silver bullet. Plus, werewolves make better neighbors
than zombies, and they tend to keep the vampire population down.
__________________________________________________________________
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
