Re: The Perfect Solution
I would not say that I, personally, am trying to break anything Rob has
done. I was simply voicing my opinion on the subject of compatability.
I have tried, to no avail, to write my programs to be as flexible as
possible in the past, but regardless of how much work on my projects,
they always seem to be broken by incompatabilities that occur with
files/routines outside the distributed includes.
The fact that the subject even comes up on this list suggests that I'm
not the only one that has the same problems to one degree or another, and
I just don't understand why all these problems can't be overcome simply
by the creation (and acceptance of) a better set of include files.
This goes beyond a preprocessor to sort out which files and routines to
use. There is alot of good code out there, but why should I need to
include 5 different libraries for structure access to write one windows
program, that includes files from 5 diffferent users, then to have to
fight all the conflicts. (that was just an example)
I have lots of code I would love to share, but every time I think I may
submit it, I remember that I also have to submit all my supporting code,
which will surely comflict with SOMETHING that someone else wrote. Or
that I'll have to support the unknown code, cause nobody else uses it...
It's just very frustrating to fight a problem that could be overcome by
the simple use of a new, standard, set of includes.
Jason
|
Not Categorized, Please Help
|
|
