[fpc-devel] Re: Class field reordering

[Florian Klämpfl]

Am 21.07.2012 23:06, schrieb Ivanko B:
> No, just reorder the fields so that they can be properly $IFDEFed as
> protected for nonLAZARUS and left (private) as is otherwise. 

Why should lazarus people have less chances to mess with private fields?
Either we make them public for all or for nobody. Of course, then
everybody has to take care of the fact that users might mess with these
fields.

> Sure not
> every filed but those the non-mainstreams developers ask. This'll
> allow  the non-mainstreams to start fixing right now.
> Florian, it's a huge headache for Martin Graeme to remember & explain
> all smallest details "what & when & why" and they can easily introduce
> bugs if  fixing their code in a hurry. As they'll remember & fix their
> code to "without cracker" they'll be informing the FPC team to delete
> related $IFDEF so on.
> 
> 2012/7/21, Florian Klämpfl <florian at freepascal.org>:
>> Am 21.07.2012 20:47, schrieb Ivanko B:
>>> I don't see cracker classes as valid code.
>>> =============
>>> Then the FPC team should eliminate the need in such crackers - via
>>> either disabling (via licencing, prisoning etc) the "impatient"
>>> [mainly because of impatient customers] non-mainstreams (non-Lazarus)
>>> or meeting needs of the non-mainstreams ( the above "{$ifdef
>>> nonLazarus}" etc ).
>>
>> So you propose we should just remove all privat/protected directives?
>>
>>
>> _______________________________________________
>> fpc-devel maillist  -  fpc-devel at lists.freepascal.org
>> http://lists.freepascal.org/mailman/listinfo/fpc-devel
>>
> _______________________________________________
> fpc-devel maillist  -  fpc-devel at lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-devel
>