22 Nov 16 22:01, you wrote to me:

 WV>>> If they are both linux gnu c, what can be different between the
 WV>>> two?

 ml>> path separators and drive letters...

 NB> He's referring to an X86 system running Linux, and an ARM device also
 NB> running Linux. There is no difference with path separators and drive
 NB> letters, but binaries can not be swapped between the two systems.

yes, i know... but winwhatever does have drive letters and the path
separators lean the other way... so true cross-platform code takes these
differences into account no matter which compiler is used... generally
speaking it comes down to using predefined variables...

eg:
  configpath := CURDRIVE + PATHSEP + currentdir + PATHSEP + "conf";
  configfile := configpath + "foo.ini";

in this example, CURDRIVE would be defined as a drive letter with a colon
(":") or an empty string... PATHSEP would be defined as
"\" or "/" depending on the current OS... yeah, it is
longer to type CURDRIVE and PATHSEP everywhere you need them but it is the
best way to do cross platform coding... at least for file access...
permissions and attributes may take other dances to learn...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin'
it wrong...
... Too much is always better than not enough.
---