OpenEuphoria

Re: The Perfect Solution

• Posted by Jason Mirwald <jmirwald at ameritech.net> Oct 19, 2004
• 530 views

Again, let's just stick a bandaid on the problem and continue re-writing
all our own libraries. Then, after a couple years of "everyone writing
the same code with similar names that is in NO WAY compatable with anyone
else's libraries", we can all start pestering Rob again to fix our file
name problems.

This is exactly the reason I haven't even attempted to code anything new
lately. Why should I waste my time writing a library to use in one of my
programs, just to find out someone else already wrote a similar library?
Then I either have to try and convince them to use mine, or debug what
I've written to run with theirs.

I've all but abandoned hope for any of my code because of these very
issues. I do this as a hobby, and I, for one, am not going to waste my
time recoding all of it again for each person who wants to use it. If
this community can manage to come to grips with the real problems that we
face, and in some small way attempt to overcome them, I would be happy to
contribute again.

If all of you could simply step out of your little boxes for just a
minute, and realize that everyone is basically writing the same code over
and over and over again (that's why it clashes so much), you might see
that the problem isn't with the slashes, and it isn't with the file names,
and it's not even with the routines. The real problem is the lack of
interest in trying to WORK TOGETHER to set up a new "standard set" of
include files for the community in general.

In all the time that will be wasted arguing about how to "fix" the
problems with the paths, we could have written a set of includes to
replace the ones that Rob distributes. Oh ... but I forgot ... we can't
break all that existing code ...

Jason