Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!ncar!ames!ucsd!ucsdhub!hp-sdd!ncr-sd!ncrlnk!uunet!mcvax!ukc!etive!hwcs!zen!frank
From: frank@zen.co.uk (Frank Wales)
Newsgroups: comp.sys.hp
Subject: Re: UNIX C compilers and ANSI C
Summary: Best guesses
Keywords: unix compiler, network services
Message-ID: <1502@zen.UUCP>
Date: 3 Feb 89 11:43:55 GMT
References: <356@ists.ists.ca>
Reply-To: frank@zen.co.uk (Frank Wales)
Organization: Zengrange Limited, Leeds, England
Lines: 40

In article <356@ists.ists.ca> mathieu@ists.ists.ca (Pierre Mathieu) writes:
>I've been trying to use function prototypes as described
>in the second edition of Kernighan & Ritchie.
>	It appears though that the cc compiler on our HP9000 series
>350 does not support these features. Can someone tell me if it is correct
>that the C compiler is a vanilla C conforming to the first edition
>of K&R? Should I abandon prototyping, especially if I want my 
>programs to be easily portable?

According to a conversation with our tech support people a couple of
days ago (we're interested in ANSI conformance too), function prototyping
(and several other funky bits of ANSI C) is expected in HP-UX
release level 7.0, tentatively due this autumn (this applies to both 300
and 800 series; yes, I know that the current 800 series release is
2.1 -- trust me).  Maybe some HP persons with their noses closer to
the grindstone can confirm or correct this.

>On a second note, I have unsuccessfully tried to figure out what
>the form of the tset command should be so that it will properly
>detect the terminal type when rlogin is used from another machine
>over an Ethernet link. I am using HP-UX 6.1 with release 6.0 of
>the Berkeley network utilities.

I'm not sure quite what you're after here; although tset can be
provided with a list of possible login places, and can also gander
in /etc/ttytype for fixed lines, rlogin doesn't come in that way;
rlogin sessions are always associated with pseudo-terminals,
such as the /dev/ttyp? chunk of devices.  Consequently,
therefore, your TERM variable (plus information like tty baud rate)
gets propagated to the remote host so that it can communicate
correctly with your terminal.  This information is what tset should
use when initialising your terminal during the login sequence, and
at any other time during the remote session.  Are you losing your
TERM variable as part of /etc/profile, for instance (we had that
problem for a time a while ago until we read the manuals more
carefully)?  Or have I missed the point of your question?

--
Frank Wales, Systems Manager,        [frank@zen.co.uk<->mcvax!zen.co.uk!frank]
Zengrange Ltd., Greenfield Rd., Leeds, ENGLAND, LS9 8DB. (+44) 532 489048 x217