[fpc-pascal] FPC 3: disabling automatic AnsiString codepage conversion

Seth Grover sethdgrover at gmail.com
Mon Apr 4 15:51:11 CEST 2016

> Not necessarily:
> if you are dealing with UTF8/UnicodeString and other codepages, it is
> quite likely, and preferred, that you have unit cwstring included.
> Michael.

Question about this: If I use cthreads, cwstring, and load my own memory
manager, what should the order in the uses clause be? I know if they are
loaded/unloaded in the wrong order you can get SIGSEGVs during shutdown.

>From my experience cthreads needs to be first. So should it be:

cthreads, my_memory_manager, cwstring


cthreads, cwstring, my_memory_manager?



Seth Grover
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-pascal/attachments/20160404/84365d71/attachment.html>

More information about the fpc-pascal mailing list