That means changing every ID setter in every example, documentation, etc. right? I'm not overwhelmed by the consequences of my question, I just don't want to do anything wrong.
On 9 Mrz., 09:08, Markus Zywitza <[email protected]> wrote: > I'm thankful for any contributions :-) > > -Markus > > 2009/3/6 Flominator <[email protected]> > > > > >http://support.castleproject.org/projects/AR/issues/view/AR-ISSUE-237141 > > > Thanks. > > > Do you want me to help with the id thing? > > > On 3 Mrz., 16:55, Markus Zywitza <[email protected]> wrote: > > > I added it to the documentation issue at donjon. > > > > -Markus > > > > 2009/3/3 Flominator <[email protected]>: > > > > > Hi, > > > > > some days ago I found out, that Castle doesn't care, if setters, > > > > getters or even whole properties were marked as private. Now I wonder > > > > why all tutorials on the Castle pages don't declare the setters of id > > > > fields as private? Why would anyone want to allow to change the id > > > > from within code? > > > > > Best regards, > > > > > Flo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
