Re: DVISP porting problem

[email protected] writes:

> In comp.lang.c I have seen O_BINARY, O_RDONLY, O_WRONLY, O_TRUNC,
> O_CREAT, which seem to be PC (Borland?) specific.

No, these symbols are POSIX and are flags to pass to the open(2)
syscall.

> A similar problem might arise with the function _setmode(..) which I
> can not find on my system.

Sorry, I don't know _setmode(), but I assume this is something defined
in dvips itself.

urs