> Someone already mentioned the issue of TIME() which also > impacts things > like SLEEP and RQM and NAP.
This is tuneable in the UniVerse config. As long as you stick to working in whole seconds - which always used to be the default - this should be fine. > I'd also wonder about port-specific usage. I believe I > worked on a Unix > box a while back where they mapped the ports so that every > time a person logged > in they got the same port number. Don't ask me exactly how > they did this. You can map ttys to port numbers using a file named unohist. But that only works if your UNIX can allocate fixed ttys to incoming connections. That is rare. > I'd also just do a quick test of the math functions. I'm > not sure every > system does the trigonometric, and extended math functions > the same way. Early > on I ran into an issue where an old box gave the same result > for two very > close but not idential numbers when you did a tangent on > them. I had to roll my > own 'fix' for that. Good point. There have also been some 'differences' between releases with respect to conversion codes and format masks. I would always opt for recompiling on the basis of 'safe rather than sorry'. But - stating the obvious I know but you would be surprised how often this trips people up - make absolutely sure that you know what to compile! Duplicate source items in different files, working copies, copies globally cataloged from another account ... Another obvious point - make sure that you recompile in the same flavor. I would always recommend using $OPTIONS flavour in your code (e.g. $OPTIONS PICK) to be doubly sure, especially if you are distributing an application. And as a minimum, make sure that you check and understand the uvconfig settings on both boxes. Regards, Brian ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
