> I have the feeling that the introduction of dynamic packages in FPC *will*
> require us to change our current RTTI from PTypeInfo to PPTypeInfo... :/
>
> Regards,
> Sven
>
So better to do it earlier rather than later ;P
Regards,
Maciej Izak (hnb)
___
On 31.05.2014 15:45, Marco van de Voort wrote:
In our previous episode, Maciej Izak said:
By Barry Kelly in comment :) :
http://stackoverflow.com/questions/3443097/what-is-the-identity-pointer-before-a-ttypeinfo-there-for
"all typeinfo fixups - pointers from one blob of typeinfo to another - a
On 08.06.2014 17:03, Graeme Geldenhuys wrote:
I've also introduced an enhanced GetPropInfo() with a signature as
follows:
function tiGetPropInfo(AClass: TClass; PropPath: string; PInstance:
Pointer): PPropInfo;
Might also profit from a declaration as "inline" :)
This one might not work as
On 2014-06-03 10:08, Sven Barth wrote:
>
> If one uses a helper function like you did then it's indeed not as bad,
> but if one doesn't...
Indeed. :) I find it is often amount managing readability of code. The
application developer doesn't need to worry to much about the difference
between platfo
Am 03.06.2014 10:26 schrieb "Graeme Geldenhuys" <
mailingli...@geldenhuys.co.uk>:
>
> On 2014-05-31 10:57, Vincent Snijders wrote:
> > I think it is possible to write code without $ifdef (valid for Delphi
> > and FPC) if you use the typeinfo unit to extract the information.
> > http://www.freepasca
On 2014-05-31 10:57, Vincent Snijders wrote:
> I think it is possible to write code without $ifdef (valid for Delphi
> and FPC) if you use the typeinfo unit to extract the information.
> http://www.freepascal.org/docs-html/rtl/typinfo/
Almost, but not quite. Good news is, it is not nearly as bad a
In our previous episode, Maciej Izak said:
> By Barry Kelly in comment :) :
>
> http://stackoverflow.com/questions/3443097/what-is-the-identity-pointer-before-a-ttypeinfo-there-for
>
> "all typeinfo fixups - pointers from one blob of typeinfo to another - are
> of type PPTypeInfo, not PTypeInfo,
>
> In FPC's TPropInfo the PropType field is PTypeInfo whereas in Delphi it is
> PPTypeInfo. I'm not sure what is actually gained by this extra level of
> indirection but it exists none the less.
>
>
By Barry Kelly in comment :) :
http://stackoverflow.com/questions/3443097/what-is-the-identity-poi
On 31.05.2014 11:57, Vincent Snijders wrote:
2014-05-31 11:48 GMT+02:00 Sven Barth mailto:pascaldra...@googlemail.com>>:
On 31.05.2014 05 :53, Kenneth Cochran wrote:
I'm attempting to port GExperts from Delphi to Lazaurus and
noticed the
definition of TPropInfo di
2014-05-31 11:48 GMT+02:00 Sven Barth :
> On 31.05.2014 05:53, Kenneth Cochran wrote:
>
>> I'm attempting to port GExperts from Delphi to Lazaurus and noticed the
>> definition of TPropInfo differs from Delphi's.
>>
>> In FPC's TPropInfo the PropType field is PTypeInfo whereas in Delphi it
>> is P
On 31.05.2014 05:53, Kenneth Cochran wrote:
I'm attempting to port GExperts from Delphi to Lazaurus and noticed the
definition of TPropInfo differs from Delphi's.
In FPC's TPropInfo the PropType field is PTypeInfo whereas in Delphi it
is PPTypeInfo. I'm not sure what is actually gained by this e
I'm attempting to port GExperts from Delphi to Lazaurus and noticed the
definition of TPropInfo differs from Delphi's.
In FPC's TPropInfo the PropType field is PTypeInfo whereas in Delphi it is
PPTypeInfo. I'm not sure what is actually gained by this extra level of
indirection but it exists none t
12 matches
Mail list logo
