General information
Category:
Coding, syntax & commands
Anybody ever implemented a portability wrapper for VFP? I mean create a class, say _VFP, that contains methods that correspond to every (most?) VFP command/function.
So, instead of writing
cText = LEFT("abc", 2)
you would write
cText = _VFP.Left("abc", 2)
I can't count the number of times that such a layer would have saved me from having to go back and rework some code. Example: for internationalization issues I want all my LEFTs to be LEFTCs. With the wrapper, I could implement the Left() method to call LEFTC and not touch my code. I could change all my _VFP.MessageBox(...) calls to actually be implemented as a MsgSvc() call or whatever.
I don't know the performance issues involved, but there certainly seem to be some merits to doing this.
Bob
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only