Re: [fpc-devel] UTF-8 string literals

> You should weigh the advantages you outline here against the disadvantages of > no longer knowing how string literals will be encoded. As a programmer, either I don't want to know (declared const without giving explicit type) or I do, then I did declare it correctly: {$codepage utf8} var u:

Re: [fpc-devel] Object checks

On 05/05/17 12:54, Pierre Muller wrote: I applied a patch in commit 36113 to trunk that substitutes RunError with HandleError. It has been applied to three functions: fpc_help_destructor, fpc_check_object and fpc_check_object_ext Thank you for doing this. In the meantime I put a slightly

Re: [fpc-devel] UTF-8 string literals

Am 06.05.2017 08:18 schrieb "Martok" : > PS: adding to the discussion over on the Lazarus ML: I just found a fourth wiki > page describing a slightly different Unicode support. This is getting ridiculous. That might be the one from Michael Schnell. Probably it should be

Re: [fpc-devel] FPC 3.0.2 for SPARC

(Personally): AWESOME! This is something that was discussed on the FPC-Pascal ML but it died. I am able to build installation bundles for SPARC running Linux (Debian) and Solaris (OpenSXCE). The fp IDE works but doesn't have libgdb support, and I've got limited time to struggle up the learning

Re: [fpc-devel] UTF-8 string literals

On Fri, 5 May 2017 16:08:41 +0200 Sven Barth via fpc-devel wrote: >[...] > Now it is fixed :D (revision 36116; maybe we should merge that to fixes > once I or someone else tested a big endian target) Thank You! Mattias

Re: [fpc-devel] Object checks

Le 06/05/2017 à 09:56, C Western a écrit : > On 05/05/17 12:54, Pierre Muller wrote: >> >>I applied a patch in commit 36113 to trunk that >> substitutes RunError with HandleError. >> It has been applied to three functions: >> fpc_help_destructor, fpc_check_object and fpc_check_object_ext >>