On Thu, Sep 08, 2005 at 02:26:02PM +0200, Tom Verhoeff wrote:
> On Wed, Sep 07, 2005 at 07:12:37PM +0200, Jonas Maebe wrote:
> >
> > On 07 Sep 2005, at 17:13, Tom Verhoeff wrote:
> >
> > >At some point in the 1.9 branch, this changed (and now it bites me).
> > >Now it silently assigns 0 to i on t
On Wed, Sep 07, 2005 at 07:12:37PM +0200, Jonas Maebe wrote:
>
> On 07 Sep 2005, at 17:13, Tom Verhoeff wrote:
>
> >At some point in the 1.9 branch, this changed (and now it bites me).
> >Now it silently assigns 0 to i on the second read. Even with -Ci as
> >option or {$I+}.
>
> This was a bug
On 07 Sep 2005, at 17:13, Tom Verhoeff wrote:
At some point in the 1.9 branch, this changed (and now it bites me).
Now it silently assigns 0 to i on the second read. Even with -Ci as
option or {$I+}.
This was a bug in 2.0 which has been fixed for 2.0.1 already.
Jonas
__
I am pretty sure that FPC 1.0.10 would give a runtime error when
attempting to read past the end of file.
E.g.
program ReadPastEOF;
var
i: Integer;
begin
readln(i);
writeln(i);
readln(i);
writeln(i);
end.
when offered a file with just one line containing one integer,
would give a run
