Re: Linking Problem

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.


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.

.

Relevant Pages

  • Re: dseek()?
    ... > The code below is a striped-down bare bones test for searching through the ... > directory structure. ... > It really seems like I 'dirp' just turns to garbage the second it's passed ...
    (comp.unix.programmer)
  • dseek()?
    ... The code below is a striped-down bare bones test for searching through the ... directory structure. ... int doDir; ... It really seems like I 'dirp' just turns to garbage the second it's passed ...
    (comp.unix.programmer)
  • Re: dirent structure wrong according to online documentation
    ... states that the directory structure doesn't have d_type ... d.cpp: In function 'int main': ... I checked the header file myself. ... is with gpp 4.32. ...
    (comp.os.msdos.djgpp)