From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Macdonald >I know that we have some PCPERFORM unix commands in >our software, and am wondering how best to get these working on a Windows system.
PCPERFORM will be easy to identify via ESEARCH, assuming your code isn't scattered hither and yon. I recommend taking the time now to analyze the purpose of these Unix commands and create standardized routines that perform the functionality for each. You'll probably find that even though there may be hundreds of PCPERFORMs throughout the application, what each does is probably very similar, representing a dozen or less standard features. So create a library of subroutines that fulfill these standard OS-level features and then when the time comes to move to another platform, you have a very finite list of OS functionality to reimplement while everything else remains unchanged. Standard functionality might include "touch", "mv", "cp", "rm"; stuff like that. These would be very simple to implement as standardized subroutines with OS-specific syntax. Taking this even to the next level, for commands like these you could parameterize a routine (say, "mv" for example) knowing that the command structure is effectively the same between the two systems - only the verb is different. This would allow you to have one routine that supports Windows, *nix, and whatever the next BBD happens to be. Loads of options that will not only help this current transition, but any future transition as well. And if it looks like a lot of work now, imagine how much work it'll be 5 years from now when you do it again. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
