In a message dated 6/9/05 8:54:44 AM Pacific Daylight Time, [EMAIL PROTECTED] writes:
<< I create a separate program file that holds lots of subroutines that represent the differences between systems. For example (maybe not the best, but most understandable), GET.PORT >> Mark I have done the same thing. You might want a routine to do EXECUTE since not all systems do it the same way or with the same options, and you can't even compile a program on one system that uses syntax from another. Another one is LOCATE which does not work the same across all versions of non-U2 Pick systems. Also how about a DO.OS.COMMAND routine :) We all know that MvBase, D3 and U2 never formed a committee to decide how to handle OS commands nor their results. So that's a bit of a mess. In fact I wrote an installer routine that runs first and ASKS the user what system they are on and then pre-loads, and pre-compiles all the relevant information for their environment. That way *I* can send the same installer to all my clients and it works fine even though they are all on disparate systems. Will Johnson Fast Forward Technologies ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
