Hello!
Russell Thamm wrote:
There appears to be an error in debug entries generated for objects. When viewing object fields under the debugger, the wrong values are shown for the right field.
I suspect that GPC did not output debugging information for the implicit VMT field in the object. Anybody out there who knows more about how the generation of debugging information in the GNU compiler works?
I was surprised to see that the Turbo Vision source code is in C++ and I see that Turbo Vision is still in the TO DO list for GPC.
Whats the current situation?
We have free Pascal sources of a TV-compatible library that cries to be ported to GPC. Once we asked at this list for volunteers eager to contribute to this project but got no reaction.
I presume that GPC can't access Gnu C++ classes.
Correct. :-(
Turbo Vision is fairly important to me so I'd be interested porting it to GPC.
This is your chance. ;-)
Frank Heckenbach wrote:
You terminate the file name with a chr (0). That's not only unnecessary (because the Name field of BindingType is a Pascal string, not a CString), but also potentially problematic: [...]
This is true now (since gpc-2.0). With gpc-1.x, it was necessary to append chr(0) explicitly to work around a bug in the GPC run time system. Some outdated documentation might still contain the workaround.
Greetings,
Peter