Re: Linking Problem
- From: Russell <rws0203nospam@xxxxxxxxxxx>
- Date: Thu, 26 May 2005 14:52:31 -0500
Wiggy <wignomore@xxxxxxxxxxxxxxx> wrote in news:d731q2$q9b$1
@nwrdmz03.dmz.ncs.ea.ibs-infra.bt.com:
> Richard wrote:
>>>According to MicroFocus
>>>in order for an executable to be portable it would have to run on a
>>>machine that has the same directory structure as the original machine.
>>
>>
>> That has just taken MicroFocus off my list of usable development
>> systems.
>>
>> They seem to have foergotten that the whole purpose of .int is that it
>> will be portable between different _types_ of systems. One should be
>> able to compile to a .int on, say, Windows and run it on Unix.
>
I haven't tried this with Unix, but you can move an int from the old
workbench 3.1 to Net Express with no problems, even without INTLEVEL. I
suppose that their might be some sort of syntax that could cause trouble,
but I haven't gone looking.
> Richard,
>
> I'd like to get further information on this statement (as in the exact
> context, and whom it came from), though my understanding is that this
> refers to linked executable files, rather than .int or .gnt code
formats.
>
> I can state that applications communicating to RDBMS's are *not*
> int-code portable, due to byte-ordering requirements of the code
> generated by precompilers (I've had this confirmed from both IBM and
> Oracle).
>
> That aside, then per Bill's email regarding the INTLEVEL compiler
> directive, and other Micro Focus documentation on creating portable
> applications, applications should be int-code portable across
platforms.
>
> SimonT.
>
>
.
- Follow-Ups:
- Re: Linking Problem
- From: Richard
- Re: Linking Problem
- References:
- Linking Problem
- From: hdumoulin
- Re: Linking Problem
- From: Richard
- Re: Linking Problem
- From: Wiggy
- Linking Problem
- Prev by Date: Re: Occurs Depending Memory Use
- Next by Date: Re: Occurs Depending Memory Use
- Previous by thread: Re: Linking Problem
- Next by thread: Re: Linking Problem
- Index(es):
Relevant Pages
|