Did you turn it on when you compiled... default is off. J

FPC doesn't even complain about range exceeded whether during compilation or runtime... isn't this an egregious violation of Pascal's strict typing philosophy? Does Turbo Pascal/Delphi behave this way as well?

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.

LogicaCMG global sponsors, Gartner Symposium, Cannes, 4th -7th November 2003

http://symposium.gartner.com/story.php.id.3323.s.5.html

Please note that LogicaCMG does not have control over content from,or availability of, this website

program blah;
type
   stringy = array[4..10] of char;
var
   C: stringy;
   D: array[2..5] of char;
procedure showstring(I:Integer);
begin
   Write(C[I]);
end;
begin
   C:='ABCDEFGHIJKLMNOPQRSTUVWXYZ';
   D:='ABCDEFGHIJKLMNOPQRSTUVWXYZ';
   Writeln(D);
   showstring(-5);
end.

FPC doesn't even complain about range exceeded whether during compilation or runtime... isn't this an egregious violation of Pascal's strict typing philosophy? Does Turbo Pascal/Delphi behave this way as well?

Ah... turns out there's -Cr... I guess one can consider it a debug on/off option. Very nifty. Just perfect.

FPC doesn't even complain about range exceeded whether during compilation or runtime... isn't this an egregious violation of Pascal's strict typing philosophy? Does Turbo Pascal/Delphi behave this way as well?

Or put -Cr in your fpc.cfg file

You might want to put -gl in there too, so if there is run time error it tells you where...J

FPC doesn't even complain about range exceeded whether during compilation or runtime... isn't this an egregious violation of Pascal's strict typing philosophy? Does Turbo Pascal/Delphi behave this way as well?

Or put -Cr in your fpc.cfg file

FPC doesn't even complain about range exceeded whether during compilation or runtime...

It does:

malpertuus: ~ >ppc386 -Cr -gl testr.pp
malpertuus: ~ >./testr
ABCD
Runtime error 201 at 0x0040DC03
0x0040DC03 SHOWSTRING, line 12 of testr.pp
0x0040DCA9 main, line 19 of testr.pp
0x0040D365

isn't this an egregious violation of Pascal's strict typing philosophy? Does Turbo Pascal/Delphi behave this way as well?

Delphi doesn't compile your program:
malpertuus: ~ >dcc32 /CC -$$R+ -$$P+ -$$V+ testr.pp Borland Delphi Version 13.0 Copyright (c) 1983,99 Inprise Corporation E:\root\testr.pp(16) Error: Incompatible types: 'stringy' and 'String' E:\root\testr.pp(17) Error: Incompatible types: 'Array' and 'String' E:\root\testr.pp(20)

Michael.

John wrote

You might want to put -gl in there too, so if there is run time error it tells you where...J

Ah... how nice... FreePascal is soooo elegant and easy to use compared to C.

I suppose this is because I'm assigning a larger string to an array[] of char that cannot hold it. Strange, even with runtime range checking on, fpc doesn't catch this problem. dcc apparently does as early as compile time... or am I missing something here?

Also, will the writing outside of array bounds in lines 16 and 17 corrupt memory even with runtime range checking on? With RRC off, I'm almost sure it will, correct?