Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site rayssd.UUCP Path: utzoo!linus!vaxine!wjh12!foxvax1!brunix!rayssd!dhb From: dhb@rayssd.UUCP Newsgroups: net.unix-wizards Subject: Re: _print/_doprnt; curses on sys III Message-ID: <479@rayssd.UUCP> Date: Wed, 20-Jun-84 12:34:50 EDT Article-I.D.: rayssd.479 Posted: Wed Jun 20 12:34:50 1984 Date-Received: Fri, 22-Jun-84 01:06:06 EDT References: <148@gargoyle.UChicago.UUCP> <1973@utcsstat.UUCP>, <4558@utcsrgv.UUCP> <1977@utcsstat.UUCP> Organization: Raytheon Co., Portsmouth RI Lines: 19 If you think that trying to bring up curses (or similar program which use _doprnt) is a problem on sys III, you should try bringing it up on VMS using the VAX11C compiler from DEC. Not only did they change the internals of the 'stdio' package, but they don't tell you what they are. Since we don't have source for VMS (does anybody?), I was forced to rewrite the printw routines in order to get them to work. I think that anyone who is writing code that will end up in the public domain should be careful to avoid any system dependencies. Given the fact that VMS now has a reasonably good implementation of the C compiler, more and more packages are going to start popping up on VMS machines. Most commercial outfits are already aware of this and take care to make sure their code is not system dependent (if possible). -- Dave Brierley Raytheon Co.; Portsmouth RI; (401)-847-8000 x4073 ...!decvax!brunix!rayssd!dhb ...!allegra!rayssd!dhb ...!linus!rayssd!dhb