[fpc-pascal] "No debugger support" in FPC3.0.4 for DOS (go32v2)

I downloaded "dos304full" and did the install. But trying to debug results in "No debugger support available" I looked into the sourcecode of the IDE and discovert that the IDE included in the downloaded DOS304FULL.zip must have been compiled with "NODEBUG" set Why is this beeing done? best reg

Re: [fpc-pascal] Concatenating CP Strings

Am 16.09.2018 um 14:31 schrieb Jonas Maebe: > [...snip...] Thank you very much for this explanation! One for the bookmarks. It just seems very odd to me to have the incredibly powerful and useful dynamic codepage concept... and then trash it on every assignment. But if that was an Emba-invention,

Re: [fpc-pascal] Concatenating CP Strings

On 16/09/18 13:31, Martok wrote: Let's say the user directs a program to "treat this file as $codepage". Therefore, I need to read it as this codepage and fill internal data structures with strings in that codepage, while keeping other operations in the system codepage (so I can't just change Def

Re: [fpc-pascal] Concatenating CP Strings

Am 16.09.2018 um 12:35 schrieb Sven Barth via fpc-pascal: > If you want the content to *be* in code page 866 without any tricks then > you need to declare a AnsiString with that code page and use that: > > === code begin === > > type > TCP866String = type AnsiString(866); That only works if the

Re: [fpc-pascal] Concatenating CP Strings

On 9/15/18 1:38 AM, Martok wrote: > Hi all, > > concatenating codepage strings is documented to be a bit weird: > > > Knowing this, how does one achieve the following? > > - have a string in any dynamic codepage > - append an

Re: [fpc-pascal] Concatenating CP Strings

On 9/15/18 10:12 PM, Martok wrote: > And another one: > > var > f: TextFile; > s: string; > begin > AssignFile(f, 'a_file.txt'); > SetTextCodePage(f, 866); > Reset(f); > ReadLn(f, s); > WriteLn(StringCodePage(s)); > readln; > end. > > That is rather useless... No, it is not. The