Thanks.

I'm actually not looking to mix them, but to recompile the old code with CCXL.

I think I've figured out that if I install LIBC.LIB.SYS in my application XL, all my new code will resolve to that, and the old code
in the next XL in the list will resolve with the CCSC libraries in it.

I'd actually like to eliminate the CCSC stuff if it mostly just recompiles using CCXL.

I may be confusing more than clarifying.

Rick.

"Jeff Kell" <[log in to unmask]> wrote in message news:8s8hca01kjf@enews1.newsguy.com...
> 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]>
>