Re: Linking Problem
- From: Russell <rws0203nospam@xxxxxxxxxxx>
- Date: Thu, 26 May 2005 16:31:02 -0500
"Richard" <riplin@xxxxxxxxxxxx> wrote in news:1117142101.207854.323030
@o13g2000cwo.googlegroups.com:
>> I haven't tried this with Unix,
>
> You do need to ensure that external names are in the correct format for
> the OS being run on, but all my file names, for example, are held in a
> system control file so that this is never a problem for me.
>
> Also there are different routines supplied with different run-times so
> there are many thinks which could stop .int s from being portable; or
> actuall stop source code from creating portable applications.
>
>> even without INTLEVEL.
>
> The defaul seems to be INTLEVEL"2" which is probably maximum
> portability.
>
>
Both Workbench 3.1 and Net Express run on Intel, so COMP-5 is okay
on both. I have mostly tried this by accident - I have never tried to
depend on it working. And GNT's do NOT work.
If you did try to get by with compiling to an INT on one system, and
running on another, note that INT's are quite slow. It does not matter
much when dealing with the user interface, but the difference in speed is
quite amazing.
.
- Follow-Ups:
- Re: Linking Problem
- From: Michael Wojcik
- Re: Linking Problem
- From: Richard
- Re: Linking Problem
- References:
- Linking Problem
- From: hdumoulin
- Re: Linking Problem
- From: Richard
- Re: Linking Problem
- From: Wiggy
- Re: Linking Problem
- From: Russell
- Re: Linking Problem
- From: Richard
- Linking Problem
- Prev by Date: Re: Linking Problem
- Next by Date: Re: In Cobol, large amount of spaces between records due to variable definition
- Previous by thread: Re: Linking Problem
- Next by thread: Re: Linking Problem
- Index(es):
Relevant Pages
|