HP3000-L Archives

March 1998, 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:
Jeff Woods <[log in to unmask]>
Reply To:
Jeff Woods <[log in to unmask]>
Date:
Tue, 24 Mar 1998 17:09:36 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
At 10:58 AM 3/24/98 GMT, Iyer Prakash wrote:
>   We have a few C libraries that we need to compile and create
>   Compatibility Mode (CM) RLs to be linked to an application we use.
>   The application itself is CM and we only create subroutines as SLs.
>
>   We are aware of the COBOLII compiler that compiles COBOL programs
>   in CM. But we do not know if there is and if yes what the 'C'
>   compiler is that can create CM object files for us.

HP never produced a CM C compiler as far as I know.  Tymlabs sold one a
long time ago, but it hasn't been seen from them in years.  CCS apparently
still sells one.

One possible way to handle your situation (assuming it will be running on
MPE/iX hardware) might be to compile the C functions in NM and use a switch
stub to call the NM routines from CM.  It's my understanding that this is
somewhat more efficient than the more common need of calling CM from NM
because the NM code can directly access the CM data, whereas CM code must
have copies made of any NM data being passed in even if passed by reference.

Just a thought....

Good luck.
--
Jeff Woods
[log in to unmask] at Tivoli Systems
[log in to unmask]   at home  [PGP key available here via finger]

Haiku by Rahul Sonnad:
   There is a chasm
   of carbon and silicon
   the software can't bridge.

ATOM RSS1 RSS2