[cap-talk] Java coding rules for capability discipline
Stiegler, Marc D
marc.d.stiegler at hp.com
Wed Nov 3 18:53:18 EST 2004
David said it better than I did. Listen to him :-)
> >>Do you for example mean no non-private static mutables?
> > Ooops. Right. Correction, no public static mutables.
> No, the requirement is to avoid any mutable state that is
> accessed implicitly. It doesn't matter whether it is exposed
> directly in a static public field, or via other static
> methods, or via instance methods that access global/static state.
> David Hopwood <david.nospam.hopwood at blueyonder.co.uk>
> cap-talk mailing list
> cap-talk at mail.eros-os.org
More information about the cap-talk