[fpc-devel] Re: Class field reordering

Martin Schreiber mse00000 at gmail.com
Sun Jul 22 12:40:42 CEST 2012

On Sunday 22 July 2012 12:06:31 Jonas Maebe wrote:
> On 22 Jul 2012, at 11:50, Martin Schreiber wrote:
> > Sorry Michael, I do not trust that the effort is worth the outcome for
> > me.
> You're really putting us between a rock and a hard place here. It's quite
> tempting to retort with "the next time I'll just commit my changes and tell
> people to deal with it, because I do not trust that the effort of
> discussing them first is worth the outcome for me".
> Of course explaining yourself and discussing costs time, and of course
> there are never guarantees about the outcome. That holds for everyone. If
> you shut out yourself from the discussion a priori, you basically force the
> other people to either a) be the "bad guys" because they don't take your
> grievances into account (mainly because they don't know enough about them
> to sensibly think about them), or b) just give up because they don't want
> to break other people's code like that
> And maybe the worst of all: the next time you have a question that requires
> thinking or discussing, people may be less inclined to spend effort on that
> because you don't return the same courtesy in the opposite situation.
I did and will do.
The situation here is especial because I must convince Michael for things that 
is of use for MSEgui only and most likely for no use in Lazarus or 
contradicts his design principles. I learned that this situation is 
unwinnable so I used mad workarounds with cracker classes instead.
Now I see that even moving private fields to protected is very difficult so I 
will search for other solutions.
An API compatible MSEgui db.pas and MSEgui specific TComponent, TReader, 
TWriter and other dependent classes is probably the best.
AFAIK TObject is the only class which depends on compiler magic? Are there 
other classes which can not be duplicated?

Thanks, Martin

More information about the fpc-devel mailing list