[fpc-devel] Re: Class field reordering

[Ivanko B]

Smth like the below:

type
  TNonCrackableClass = class
private
  fldPrivate1: integer;
  fldPrivate2: styring;
{$ifndef nonLazarus}
  fldPrivate3: real; // for LAZARUS
{$else}
protected
  fldPrivate3: real; // for MSEgui/FPgui
{$endif}
protected
 fldProtected1: string
public
  [..]
end;

2012/7/22, Ivanko B <ivankob4mse2 at gmail.com>:
> No, just reorder the fields so that they can be properly $IFDEFed as
> protected for nonLAZARUS and left (private) as is otherwise. 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
>>
>