Re: [fpc-pascal] Type of file mode variable

2011-03-18 Thread Jürgen Hestermann
Jonas Maebe schrieb: I didn't find fminout and the other constants mentioned at this link. It describes the values you can assign to filemode and their effect. Does that mean, that only 3 values for filemode (0, 1 and 2) exist? Then it is quite confusing to group the filemode declaration and

Re: [fpc-pascal] Type of file mode variable

2011-03-18 Thread Michael Van Canneyt
On Fri, 18 Mar 2011, Jürgen Hestermann wrote: Jonas Maebe schrieb: I didn't find fminout and the other constants mentioned at this link. It describes the values you can assign to filemode and their effect. Does that mean, that only 3 values for filemode (0, 1 and 2) exist? Then it is

[fpc-pascal] Type of file mode variable

2011-03-17 Thread Jürgen Hestermann
In the file \lazarus\fpc\2.4.3\source\rtl\inc\systemh.inc I found the following definitions: { file input modes } fmClosed = $D7B0; fmInput = $D7B1; fmOutput = $D7B2; fmInOut = $D7B3; fmAppend = $D7B4; Filemode : byte = 2; If I assign Filemode := fmInOut I get a constant range check

Re: [fpc-pascal] Type of file mode variable

2011-03-17 Thread Jonas Maebe
On 17 Mar 2011, at 19:07, Jürgen Hestermann wrote: If I assign Filemode := fmInOut I get a constant range check error (at compilation time) which is clear because all constants are larger than byte. Is this a bug? No. See http://www.freepascal.org/faq.var#filemode for more info.

Re: [fpc-pascal] Type of file mode variable

2011-03-17 Thread Jürgen Hestermann
Jonas Maebe schrieb: On 17 Mar 2011, at 19:07, Jürgen Hestermann wrote: If I assign Filemode := fmInOut I get a constant range check error (at compilation time) which is clear because all constants are larger than byte. Is this a bug? No. See

Re: [fpc-pascal] Type of file mode variable

2011-03-17 Thread Jonas Maebe
On 17 Mar 2011, at 19:24, Jürgen Hestermann wrote: Jonas Maebe schrieb: On 17 Mar 2011, at 19:07, Jürgen Hestermann wrote: If I assign Filemode := fmInOut I get a constant range check error (at compilation time) which is clear because all constants are larger than byte. Is this a bug?