[fpc-devel] Re: Class field reordering

Martin Schreiber mse00000 at gmail.com
Mon Jul 23 06:33:17 CEST 2012

On Sunday 22 July 2012 15:22:44 Hans-Peter Diettrich wrote:
> > Some fields are kept private to ensure that the terms of the contract
> > can be met. Making them public/protected means that the terms of the
> > contract can be broken by Developer A, when the code of developer B
> > depends on the terms being rigorously enforced, and his code can go very
> > wrong.
> IMO there exist two use cases for (base) classes: by end users and by
> component writers. Both have different goals and problems, which rarely
> can be covered by an single set of properties. When an end-user never
> should be allowed to write into some field, a developer may have reasons
> to do so.


More information about the fpc-devel mailing list