Basically not much difference, file I/O and number formatting works quite exactly the same, the only difference is that Unix has no CR+LF in text files and directory paths under Unix don't use backslashes (DOS/Windows paths can use foreward slashes though, so they are compatible in one direction). *)robertmiles hat geschrieben:I've never used Linux, so I doubt that I'm ready.
The problem is that some modules work with static variables (in different calltree depths, i.e. a library has its own set), there is not one set of globals that can be saved - and the calculation is not homogenous over the time, which means you cannot just start a big outer loop at 515, when you already have done 1 to 514. Some higher loop counts need a few intermediate results of the lower ones, which are "hidden" statically inside of the modules.
It would be good if the developer could do that - but he might have the same problem, as the program uses a library he has not developed but is just using parts of it.
Definitely not a quick task to do :-/
*) OT : This slash/backslash thing even worked with the command line of very early DOS versions, you could set the SWITCHCHAR to Minus (=> program options working like "dir -s" instead of "dir /s") and use the slash as a directory separator then. (Afaik. the default switch character "/" had been a relic from a basic CP/M compatibility of DOS1, refer to the Ralf Brown interrupt lists if you're interested in that stuff or have grey hair to already know about it)