From: pavenis AT lanet DOT lv Message-ID: To: Waldemar Schultz , djgpp AT delorie DOT com Date: Mon, 27 Sep 1999 19:15:16 +0300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: GPC File I/O (was PASCAL to C) In-reply-to: <37EF434B.C966181C@ma.tum.de> X-mailer: Pegasus Mail for Win32 (v3.12a) Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On 27 Sep 99, at 12:13, Waldemar Schultz wrote: > After all I am using GPC 2.0(2.7.2.1) GNU Pascal to compile my old > Turbo-Pascal(5.0) Files rather than translating them to C. Some time ago it was written that GPC-2.0 is now for "masohists and archeologists" only. When I built DJGPP port of egcs-1.1.2 (which now is in directory v2gnu/egcs in DJGPP distribution) I included also 19990118 beta version of GPC which should be stable enough (and have many new features). I suggest trying it instead of outdated GPC- 2.0. You also need to install gcce112b.zip and gpce112b.zip to use Pascal. Don't ask me for much details about GPC. Perhaps GPC mailing list would be better place. See http://agnes.dida.physik.uni-essen.de/~gnu-pascal/ for more info Andris > > After some hours of reading the info I found out that "Assign()" is not > implemented; > but there is a workaround using "Bind" etc. (don't know why, either). > Then I found out, that the Borland directives {$I-} and {$I+} > are not supported and produce garbage error messages. > After removing those directives from the Pascal source it compiles fine. > > The only thing I can't heck for now is how to use some equivalent for > Borlands > built-in variable "Ioresult" for testing the success of I/O operations. > > Could someone please give me a hint how to catch bad I/O operations > like "File not found" or "Can't open" and that other related stuff in > GPC. > > Any help is highly appreciated. Thank you all out there.