[fpc-pascal] Language constructs and types that dependent upon system unit

Felipe Monteiro de Carvalho felipemonteiro.carvalho at gmail.com
Thu Jan 19 21:40:11 CET 2017

On Thu, Jan 19, 2017 at 8:15 PM, gabor <gabor at poczta.onet.pl> wrote:
> problems with initialization/finalization sections).
> I know that following types require extra code:
> object, class, sting, dynamic array, try..except.
> What else should I avoid?

I think it is a huge exaggeration to rule out all of that. I think
that most of this stuff from basic language or system unit should work
just fine. Indeed some might not work, but most should work.

If you use the unit cmem (or even better if you make your own memory
manager that redirects to the C side), I don't see why
object/class/string/dynamic arrays should fail, when used internally
in the Pascal side.

try...except will probably indeed not work, because C often uses a
different exception mask than FPC or something like that.

I didn't try it myself recently, but instead of going bare-bones I
would rule out stuff that fails when they fail, not beforehand suppose
they won't work.

Felipe Monteiro de Carvalho

More information about the fpc-pascal mailing list