[fpc-pascal] Language constructs and types that dependent upon system unit
noreply at z505.com
Fri Jan 20 00:10:52 CET 2017
On Thu, January 19, 2017 1:28 pm, gabor wrote:
> I was hoping that maybe there is an easy answer. But I understand.
The easy answer is just to use the system unit and have no fear...
The main issue with using fpc with C is when you try to use classes or try
to use C++ classes
As objects are not so portable across languages.. Every language has their
own object format. Also strings, being reference counted, will cause some
issues unless you convert them to pchar when sending in as a read only to
C, or if C writes to the string buffer you have to send a buffer in that
is allocated by you (or a fixed buffer) rather than sending in an
Ansistring. Memory managers will conflict. Or use shared memory manager.
But C knows nothing about what a modern pascal reference counted
ansistring is.. it has no information about it.
More information about the fpc-pascal