On Fri, Nov 22, 2013 at 2:55 PM, Martin Schreiber <[email protected]> wrote:
> On Friday 22 November 2013 18:29:49 Marcos Douglas wrote:
>
>>
>> But we can't do this:
>> "
>> type
>> tfoo = object //rtti is off
>> private
>> fprop1: int32;
>> fprop2: int32;
>> fprop3: int32;
>> protected
>> {$rtti on}
>> property prop1: int32 read fprop1 write fprop1; //streamed
>> {$rtti off}
>> property prop2: int32 read fprop2 write fprop2; //not streamed
>> public
>> {$rtti on}
>> property prop3: int32 read fprop3 write fprop3; //streamed
>> {$rtti off}
>> end;
>> "
>>
> Why not? '{$rtti off}' is another possible setting. The last {$rtti off} in
> the example is not necessary.
Do you would rather have two possibilities??
So, is this right?
"
type
tfoo = object //rtti is off
private
fprop1: int32;
fprop2: int32;
fprop3: int32;
protected
{$rtti streaming}
property prop1: int32 read fprop1 write fprop1; //streamed
{$rtti off}
property prop2: int32 read fprop2 write fprop2; //not streamed
public
{$rtti streaming}
property prop3: int32 read fprop3 write fprop3; //streamed
end;
"
IMO is more readable using:
{$rtti on} {$rtti off}
--
Marcos Douglas
------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
mseide-msegui-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
