According to Christian Wendt:

PG>The same stuff as in Borland's CRT, isn't it? Hmm. no - several stuff. move; declaration of byte... paramstr,paramcount (the date is 27.10.96) - seems to be an extract of tools/system.pas of BO5

We are speaking of different Units: You mean `bpcompat.pas' while I am speaking of `bpcompat.zip' which contains `system.pas', `crt.pas', etc.

hmm. is the type of "file" specified in the ISO /Extended?

You mean the internal structure of the `file' type? No.

would it be possible to define it similar to TP/BP? there's a list of procedures inwith the file "record" - they specify the functions to init/flush/writebuffer/readbuffer (theoretical you could do the same with an object...)

It's defined in a quite different way. The record contains a lot of interesting information about the file, but no `hooks'. The actual input/output is done via `ordinary' functions written in C.

But be invited to implement those `hooks' in the GPC RTS.

PG>Of course. But a CRT Unit could use these sequences to access the PG>terminal in a portable way. Yes... transparent for the programmer...

Everything is transparent for the programmer since you have the source code of everything. :-)

Peter

Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski@uni-essen.de - http://home.pages.de/~peter.gerwinski/ [970201] maintainer GNU Pascal [970420] - http://home.pages.de/~gnu-pascal/ [970125]