Re: [fpc-pascal] writeln in fpc 2.0.2

2006-05-31 Thread Michael Van Canneyt
On Tue, 30 May 2006, Gustavo Enrique Jimenez wrote: > You MUST remove the CRT unit. > It's mentioned explicitly in the documentation that you are not allowed to use it for CGI. > I've removed all crt references. My cgi app works perfectly now. As an unexpected side effect, this app works

Re: [fpc-pascal] writeln in fpc 2.0.2

2006-05-30 Thread Gustavo Enrique Jimenez
> You MUST remove the CRT unit. > It's mentioned explicitly in the documentation that you are not allowed to use it for CGI. > I've removed all crt references. My cgi app works perfectly now. As an unexpected side effect, this app works perfectly also with Apache for windows. Thank you, than

Re: [fpc-pascal] writeln in fpc 2.0.2

2006-05-30 Thread Gustavo Enrique Jimenez
You MUST remove the CRT unit. It's mentioned explicitly in the documentation that you are not allowed to use it for CGI. ok ! I will remove crt references. Sorry for not read the docs Thank you very much (Marco and Michael)... Gustavo Enrique Jiménez _

Re: [fpc-pascal] writeln in fpc 2.0.2

2006-05-30 Thread Michael Van Canneyt
On Tue, 30 May 2006, Gustavo Enrique Jimenez wrote: > I use Lazarus. So, I've upgraded fpc from 1.0.10 to 2.0.2 . > > I've recompiled my cgi apps, and now something is wrong: lines with > more than 80 char writed with writeln seems to be "truncated" at > position 80. A #10 char follows, an th

Re: [fpc-pascal] writeln in fpc 2.0.2

2006-05-30 Thread Marco van de Voort
> ps: Deep in the code, it is possible that crt unit is still linked > (the cgi app comes from an old turbopascal console app). I think this is the primary problem, in combination with your terminal emulator and/or settings. - What do you use for console? - Some X program like xterm or gnomecon

[fpc-pascal] writeln in fpc 2.0.2

2006-05-30 Thread Gustavo Enrique Jimenez
I use Lazarus. So, I've upgraded fpc from 1.0.10 to 2.0.2 . I've recompiled my cgi apps, and now something is wrong: lines with more than 80 char writed with writeln seems to be "truncated" at position 80. A #10 char follows, an then the rest of the line. If I send the output to a text file, c