2010/1/1 Magnus Danielson <[email protected]>: > Steve Rooke wrote: >> But what about a single code to cover nix and DOS/Windows? > > It should be possible to the best of my knowledge... I haven't played with > DOS or Windows programming for years. Except for some simple GPIB exercises, > it must have been back in mid 90ies or something. Anyway, I assume POSIX > sockets and serial I/O exists. The only real cleanup is the GUI interface, > where wxWidget or GTK might be the options to consider.
Well, for all the nix variants, standard POSIX sockets and tty code will be the same but I have no experience of DOS/Windows system calls and functions period. As for the user interface, the existing application looks just like a DOS console application so there is no windowing code to my mind. It should be able to do it in a similar way with curses but I'm not sure how the screen is written. I do know that there is a fair amount of processor load, including a lot of system calls. On my system, running LH under wine takes the equivalent of 1 CPU on my quad core. That's a fair amount of processor load but it would only be fair to see what that is likely to be once a native port is done and the application could be profiled then. Cheers, Steve > Cheers, > Magnus > > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > -- Steve Rooke - ZL3TUV & G8KVD A man with one clock knows what time it is; A man with two clocks is never quite sure. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
