Re: [fpc-devel] new rtl- packages

2014-01-08 Thread Thaddy
Hoi, Marco, native win32 ben je vergeten. matrix... Groetjes, Thaddy On 6-1-2014 13:10, Marco van de Voort wrote: To whom it may concern, fyi The RTL was getting quite big, and is compiled 4-5 times per make all, so with a major branch splitting off in the next half year and the end of the

[fpc-devel] programmers guide 2.6 issue

2014-01-08 Thread John Lee
In Pascal programmers guide v2.6 Feb 2013 it explains how to use {$I ... } to include compiler information eg version string, time string etc so one can include eg in a writeln, but it does not mention not the optimisation level at which program was compiled. Is this an omission or is this info

Re: [fpc-devel] programmers guide 2.6 issue

2014-01-08 Thread Pierre Free Pascal
Hi John, in the scanner.pas unit procedure dir_include, code starting around line 2324 on current trunk, you can see that there are only a few special names allowed. If there is no match, the compiler looks for an environment string with that name. This might be the solution for your

Re: [fpc-devel] Explanation about code page-aware AnsiStrings

2014-01-08 Thread Hans-Peter Diettrich
Jonas Maebe schrieb: http://wiki.freepascal.org/FPC_Unicode_support (only Sections 1 to 3; 4 and later are older and mostly either incomplete or wishful thinking). Just a note on RawByteString concatenation: Delphi concatenates RawByteStrings to the dynamic encoding of the *first* string,

Re: [fpc-devel] programmers guide 2.6 issue

2014-01-08 Thread John Lee
Thanks - I'd thought that I'd seen somewhere (here?) that one could get the opt info into compiler string somehow thought it'd be there hence so doc . Maybe it is somewhere else not under {I ...}? On 8 January 2014 13:35, Pierre Free Pascal pie...@freepascal.org wrote: Hi John, in the

Re: [fpc-devel] Explanation about code page-aware AnsiStrings

2014-01-08 Thread Sven Barth
Am 08.01.2014 15:58 schrieb Hans-Peter Diettrich drdiettri...@aol.com: Delphi concatenates RawByteStrings to the dynamic encoding of the *first* string, the appended strings eventually are converted before concatenation. Special handling of strings with the same encoding is not required. I.e.

Re: [fpc-devel] programmers guide 2.6 issue

2014-01-08 Thread Sven Barth
Am 08.01.2014 14:21 schrieb John Lee johnel...@gmail.com: In Pascal programmers guide v2.6 Feb 2013 it explains how to use {$I ... } to include compiler information eg version string, time string etc so one can include eg in a writeln, but it does not mention not the optimisation level at which

Re: [fpc-devel] Explanation about code page-aware AnsiStrings

2014-01-08 Thread Hans-Peter Diettrich
Sven Barth schrieb: Am 08.01.2014 15:58 schrieb Hans-Peter Diettrich drdiettri...@aol.com mailto:drdiettri...@aol.com: Delphi concatenates RawByteStrings to the dynamic encoding of the *first* string, the appended strings eventually are converted before concatenation. Special handling of

Re: [fpc-devel] Explanation about code page-aware AnsiStrings

2014-01-08 Thread Sven Barth
On 08.01.2014 19:57, Hans-Peter Diettrich wrote: Sven Barth schrieb: Am 08.01.2014 15:58 schrieb Hans-Peter Diettrich drdiettri...@aol.com mailto:drdiettri...@aol.com: Delphi concatenates RawByteStrings to the dynamic encoding of the *first* string, the appended strings eventually are

Re: [fpc-devel] DOS GUI

2014-01-08 Thread Travis Siegel
On Dec 26, 2013, at 1:17 PM, Jim Leonard wrote: On 12/26/2013 11:35 AM, Pierre Free Pascal wrote: It would be nice to have it publicly available. Seconded. I agree with this assessment as well. ___ fpc-devel maillist -

Re: [fpc-devel] programmers guide 2.6 issue

2014-01-08 Thread John Lee
You are making it sound v complicated - but the settings eg for the main program eg might be -O3 or -O2 or something are meaningful - most people don't mess with them anyway. I feel sure that I've seen somewhere how to get them into compiler string, but can't remember how! J On 8 January 2014

Re: [fpc-devel] programmers guide 2.6 issue

2014-01-08 Thread Sven Barth
Am 08.01.2014 22:16 schrieb John Lee johnel...@gmail.com: You are making it sound v complicated - but the settings eg for the main program eg might be -O3 or -O2 or something are meaningful - most people don't mess with them anyway. I feel sure that I've seen somewhere how to get them into

Re: [fpc-devel] Explanation about code page-aware AnsiStrings

2014-01-08 Thread Hans-Peter Diettrich
Sven Barth schrieb: On 08.01.2014 19:57, Hans-Peter Diettrich wrote: It looks to me, however, that no conversion occurs at all! The strings are only concatenated as they are. Same for a concatenation of (global) RawByteString variables. This of course were not a desireable implementation :-(

Re: [fpc-devel] Explanation about code page-aware AnsiStrings

2014-01-08 Thread Sven Barth
On 08.01.2014 23:54, Hans-Peter Diettrich wrote: Sven Barth schrieb: On 08.01.2014 19:57, Hans-Peter Diettrich wrote: It looks to me, however, that no conversion occurs at all! The strings are only concatenated as they are. Same for a concatenation of (global) RawByteString variables. This