RE: win32lib & global functions
- Posted by Andy Serpa <ac at onehorseshy.com> Oct 03, 2003
- 349 views
Wolf wrote: > > > > Same thing with all the functions in tk_trim.e -- trim(), compress(), > > split(), etc. -- these are all functions I've already got that may or > > may not do the same thing as those versions. Win32lib is hogging all > > the good function names! > > Couldn't we call all these W32_trim(), W32_compress(), or some such > > thing? > So, why not rename all *your* custom functions accordingly: > ... as_trim(), as_compress(), etc, ... or whatever ... > ... or are you suggesting _everyone_else_ should re-write all their > existing code? Are people including win32lib.e so they can use abs() or trim()? I thought it was a Windows library. It is better programming practice to use non-generic names, and any transition needed does not have to be painful. A simple, optional alias file using the original names will do if people are using these functions in their own code and don't want to update...