HP3000-L Archives

October 2000, Week 2

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:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Fri, 13 Oct 2000 22:31:22 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Rick Ingham wrote:
>
> Are there any gotchas in taking old 'C' code for the CCSC compiler and recompiling it using HP's C/iX compiler?  I'm looking at
> native compiler, not the Posix one.  [...snip...]

C is somewhat unique in that the library code relies on some
initialization to be done at startup time.  On MPE, for example, you
implicitly get LIBCINIT.LIB.SYS included in your code.  It can't just
start from scratch on it's own, especially the I/O routines.

As MPE had no such mechanism, native C includes this behind your back.
The CCSC code had to "roll it's own" in the absence of any MPE support
initially, and never was fixed for NM or HP's own C/iX libraries.

So no, I wouldn't expect them to coexist in XLs.  Just as there are
issues between C/iX [MPE mode], c89 [Posix mode], and gcc [GNU] code
in the official HP arena, you are begging for trouble with a 3rd party
in the mix.

I'm sure the resident C/c89/gcc gurus can elaborate, I'll leave it to
them; but you're asking for trouble.

You should be able to port it to C/iX or gcc without too many issues
(I've not used CCSC's compiler, but was *this close* to getting it in
the classic days).

We did use Trax/C before getting XDB though, so it may not be as
difficult to port as you imagine.

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2