HP3000-L Archives

August 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Walter Murray <[log in to unmask]>
Reply To:
Walter Murray <[log in to unmask]>
Date:
Tue, 22 Aug 2000 18:10:22 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
Ken Graham ([log in to unmask]) wrote:
: Dennis Handly ([log in to unmask]) wrote:
: >There use to be only one language organization doing the work.  6 to 7
: >years ago, CSY went its own way.
: >So there is one group doing HP-UX (IA64 and PA) and one for MPE/iX.

: It is my understanding that this is not the case at least for C.
: There is one group doing the language and they do it for HP-UX, and
: secondarily
: for MPE.  That is why you can compile MPE C code on an HP-UX box, and bring
: the object modules over to the MPE to link them, and it works just fine.
: The argument from the lab against making any changes to the C compiler was
: that it was the same compiler as the one on HP-UX.

Dennis is correct.

HP C/HP-UX and HP C/iX have a common ancestry and still have much
in common.  Whenever there is a request to change a behavior in C/iX,
one of the factors considered is whether it would create an
incompatibility with C/HP-UX.

Walter Murray
Hewlett-Packard
HP C/iX

ATOM RSS1 RSS2