To the compiler developers:
In FPC 2.0.0
- Are the fields TTypeData.IntfParent, IID, IIDStr and IntfUnit valid for tkInterface?
- Is TTypeData.IntfParent really PPTypeInfo or is it PTypeInfo?
- How is TTypeData.IntfUnit aligned?
Thanks, Martin
Mailing lists / fpc-devel / 2005-06
RTTI for interface (2)
5 messages · 3 people ·
- Martin Schreiber 2
- Peter Vreman 2
- Florian Klaempfl 1
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Show quoted text 5 lines
To the compiler developers:
In FPC 2.0.0
- Are the fields TTypeData.IntfParent, IID, IIDStr and IntfUnit valid for
tkInterface?
Looking at the compiler sources: tkInterface is written the same as tkClass.
- Is TTypeData.IntfParent really PPTypeInfo or is it PTypeInfo?
I guess it'll then be PTypeInfo when the compiler is fixed
- How is TTypeData.IntfUnit aligned?
It doesn't need alignment. It consists only of chars.
Peter Vreman wrote> - How is TTypeData.IntfUnit aligned? It doesn't need alignment. It consists only of chars.
So offset IIDStr->IntfUnit is 256 (IIDStr = shortstring = string[255])? Or IntfUnit starts after last char of IIDStr?
Show quoted text 7 lines
On Monday 13 June 2005 12.59, Peter Vreman wrote:
> > - How is TTypeData.IntfUnit aligned?
>
> It doesn't need alignment. It consists only of chars.
So offset IIDStr->IntfUnit is 256 (IIDStr = shortstring = string[255])?
Or IntfUnit starts after last char of IIDStr?
It is not yet defined. The compiler part is not implemented yet
Peter Vreman wrote 11 lines
>On Monday 13 June 2005 12.59, Peter Vreman wrote:
>
>>>- How is TTypeData.IntfUnit aligned?
>>
>>It doesn't need alignment. It consists only of chars.
>
>So offset IIDStr->IntfUnit is 256 (IIDStr = shortstring = string[255])?
>Or IntfUnit starts after last char of IIDStr?
It is not yet defined. The compiler part is not implemented yet
If you've trouble to get something to work, submit a bug report with a small example which shows the problem.