Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA
Path: utzoo!utcs!lsuc!pesnta!hplabs!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: DEC C system
Message-ID: <4882@ucbvax.ARPA>
Date: Sat, 16-Feb-85 15:30:07 EST
Article-I.D.: ucbvax.4882
Posted: Sat Feb 16 15:30:07 1985
Date-Received: Sun, 17-Feb-85 12:30:23 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 31

From: Rudy.Nedved@CMU-CS-A.ARPA

Hi. Forgive me if someone has already sent information about this
in the past. I am relatively new user of the DEC C compiler and
run-time system.

I am trying to get a handle on the following pieces of information:

   a) Is there a "quick way" to translate a "unix" file descriptor
      (returned by open/creat or by fileno(<FILE *>)) into an
      active QIO channnel? My definition of quick is avoiding "system
      calls"....I am hoping there is some known table hidden but
      accessible in the run-time library. I am trying to write some
      "companion" routines to the provided "unix" primitives.

   b) Does anyone know the parameters to c$$doprint? Is this similiar to
      _doprnt in Unix land or are the names similiar to the confuse
      the hackers like me?

   c) Is there a way to tell the "unix" primitives to not play with input
      and output to the terminal. I put the terminal into passall mode and
      noecho but discovered the input routines (fgetc(stdin)) waits until
      carriage return is hit (the stdin->_cnt goes up) and then returns the
      input but with the carriage return translated to a linefeed. The same
      "line oriented" action happens on output. I agree with the behaviour
      system it makes perfect sense in an RMS enviroment but I am dealing
      with an interactive terminal talking to a human and humans are not
      files.....

Thanks,
-Rudy