Hello Jean,

Compiling Splash code on HPUX doesn't require any changes, as long as your
HPUX box is PA/RISC. This is because the output of splash is pure pa/risc
assembler. You WILL be stuck though, or have a problem if/when HP decides to
stop PA/RISC.
A different, more labour intensive but more long-term solution would be to
convert the splash code to something else, like C or C++.

<plug>
Ordina-Denkart offers an SPL to C++ cross compiler that automatically
converts spl/splash code to C++
</plug>

You also will require some solution for your intrinsic calls inside your
splash code since these functions don't exist as such on hpux.

<plug>
A good solution here is MPUX, which supports practically all intrinsics, and
is (the only commercial solution that is) compatible with splash. just link
the mpux runtime library to the splash object code and voila.
Obviously MPUX is also compatible with the SPLtoC++ cross compiler.
</plug>

If you don't want third party add-ons or write your own intrinsic
replacements, you will need to change part of your splash code to call
native unix system calls instead of intrinsics.

regards,

Geert Coelmont
HP3000 migrations product manager
Ordina-Denkart


On Tue, 5 Jul 2005 14:13:26 -0400, Northern Credit Bureaus Inc
<[log in to unmask]> wrote:

>Is the conversion process from programs compiled with Splash under MPEix to
Splash under HPUX necessitate any programming changes or is it transparent
from one platform to the other.
>
>I would like to hear from people who have gone from MPEiX to Unix.
>
>
>Thanks,
>
>Jean Huot
>Northern Credit Bureaus Inc.
>(819) 762-4351
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *