OpenEuphoria

Re: win32lib & global functions

• Posted by Pete Lomax <petelomax at blueyonder.co.uk> Oct 03, 2003
• 379 views

On Fri,  3 Oct 2003 13:52:06 +0000, Andy Serpa <ac at onehorseshy.com>
wrote:

>
>
>Wolf wrote:
>>=20
>>=20
>> > 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()?
No, but people including win32lib are using abs() and trim().
>I thought it was a Windows library.
Yes...
>It is better programming practice to use non-generic names,=20
LOL, pot calling the kettle black, methinks.
>and any transition needed does not have to be painful.
> A simple, optional alias file using the original names will do=20
>if people are using these functions in their own code and don't want to=20
>update...
So why not move your own functions to your own, optional include file
that you use when you are not including win32lib?

Why get Derek to do this and potentially upset a large number of
people and break alot of existing code in the archives, when you could
just as easily do it without having to worry about that?

Pete