Hi,
I've just noticed that with FPC 1.0.6 on Win32
one cannot pass empty string as a parameter - Access violation in SYSWIN32_SETUP_ARGUMENTS.
I've just tried:

program tester;
begin
end.

.\tester ""
Runtime error 216 at blah blah blah

Is this issue fixed in 1.0.7 or 1.1 ?

Regards,
Adam Naumowicz

====================================================================== Department of Applied Logic fax. +48 (85) 745-7662 Institute of Computer Science tel. +48 (85) 745-7559 (office) University of Bialystok e-mail:
Sosnowa 64, 15-887 Bialystok, Poland http://math.uwb.edu.pl/~adamn/ ======================================================================

Adam,

checked it with 1.0.8-pre1 win32 and the current 1.1 win32, works fine.

Hi,

Armin Diehl wrote

checked it with 1.0.8-pre1 win32 and the current 1.1 win32, works fine.

Thanks, this probably means that, indeed, it has been fixed. BTW, I happened to use Win98, on what Win32 platform did you check it? I suppose such basic thing like program parameters is handled by the kernel procedures, and AFAIK various winbloze flavours are not fully compatible...

Still, I'll be more than grateful if someone from the developers could comment on that. If it has really been fixed in development releases after 1.0.6, I'd like to know what was the cause of the error. Best wishes,

Adam Naumowicz

====================================================================== Department of Applied Logic fax. +48 (85) 745-7662 Institute of Computer Science tel. +48 (85) 745-7559 (office) University of Bialystok e-mail:
Sosnowa 64, 15-887 Bialystok, Poland http://math.uwb.edu.pl/~adamn/ ======================================================================

The parsing of the program parameters is handled in the FPC RTL and independent of the Windows version.

Why not download a recent snapshot eg of win32 v1.0.7 (which is effectively the upcoming v1.0.8 release) or a v11 snapshot, and try it yourself - that's why we (normally) do regular snapshots!

I've tried it on win95 & win me... & it's ok.

Regards John

checked it with 1.0.8-pre1 win32 and the current 1.1 win32, works fine.

Thanks, this probably means that, indeed, it has been fixed. BTW, I happened to use Win98, on what Win32 platform did you check it? I suppose such basic thing like program parameters is handled by the kernel procedures, and AFAIK various winbloze flavours are not fully compatible...

> Is this issue fixed in 1.0.7 or 1.1 ?

Still, I'll be more than grateful if someone from the developers could comment on that. If it has really been fixed in development releases after 1.0.6, I'd like to know what was the cause of the error. Best wishes,

Adam Naumowicz

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

i checked it on 2k and xp

Hi,

John wrote

Why not download a recent snapshot eg of win32 v1.0.7 (which is effectively the upcoming v1.0.8 release) or a v11 snapshot, and try it yourself - that's why we (normally) do regular snapshots!

The reason is quite simple - no windows at hand and not enough time ;-(

I've tried it on win95 & win me... & it's ok.

Thanks. Seems the upgrading is unavoidable, though I'm, to some extent, obliged to using the same stable compiler versions on Linux, Solaris and Win32, and this means some extra work for me AFAIR some 'self'-related changes in 1.1.

All the best,
Adam Naumowicz

====================================================================== Department of Applied Logic fax. +48 (85) 745-7662 Institute of Computer Science tel. +48 (85) 745-7559 (office) University of Bialystok e-mail:
Sosnowa 64, 15-887 Bialystok, Poland http://math.uwb.edu.pl/~adamn/ ======================================================================

Adam Naumowicz wrote

Thanks. Seems the upgrading is unavoidable, though I'm, to some extent, obliged to using the same stable compiler versions on Linux, Solaris and Win32

Forgot to ask: what about Solaris (i386) binary snapshot distro of 1.1? Or do I have to compile it myself from the sanpshot sources?

Regards,
Adam Naumowicz

====================================================================== Department of Applied Logic fax. +48 (85) 745-7662 Institute of Computer Science tel. +48 (85) 745-7559 (office) University of Bialystok e-mail:
Sosnowa 64, 15-887 Bialystok, Poland http://math.uwb.edu.pl/~adamn/ ======================================================================

The core developpers don't have a Solaris i386 machine that is turned on for 24/7 so there can be no cron-job installed to build it.

Hello,

Peter Vreman wrote

The core developpers don't have a Solaris i386 machine that is turned on for 24/7 so there can be no cron-job installed to build it.

After some adjustments I managed to compile the new compiler using the rtl of 1.0.6 [2002/04/29] (mostly getting rid of unix/posix/linux related complaints). But I think it doesn't make much sense when the RTL is not recompiled. So then I thought of compiling the RTL myself, but got stuck as the content of current rtl/sunos is quite different from that of my old 1.0.6.
What should I do to compile the system unit?

Regards,
Adam Naumowicz

====================================================================== Department of Applied Logic fax. +48 (85) 745-7662 Institute of Computer Science tel. +48 (85) 745-7559 (office) University of Bialystok e-mail:
Sosnowa 64, 15-887 Bialystok, Poland http://math.uwb.edu.pl/~adamn/ ======================================================================

I have duplicated this problem with the released 1.06 version, under Windows 2000 [Version 5.00.2195]. Source file (listparams.pas):

  var
    i: integer;
  begin
    for i := 0 to paramcount do begin
      writeln('[',i,'] ',paramstr(i));
    end;
  end.

Command line:

listparams a b "" c

Output:

Runtime error 216 at 0x00402602
0x00402602
0x004020B6
0x00401E5B
0x00401D6D
0x00401059

I hope this helps.

- Rich