RE: Standardisation between Win libraries
Phew, I guess it's more difficult than I first thought.
So, basically we're looking at many MS Windows (ignoring Linux at the
moment - sorry) libraries, that each do much the same thing, but with
differences (bits missed, etc). Each of them written to manage the
tasks that the writer wanted to do at the time, but not complete enough
for a wider range of tasks. Each of them sits somewhere on the Euphoria
Path and there can, potentially, be many copies of them (Lots of people
supply a copy of win32Lib, ewin32API, win32R, etc; along with their
application) - I already have 12 copies of win32lib that came in various
zips.
I agree with Derek on the sensibilities of not simply including ALL the
function even if not needed. I'm not sure about the absolute need for
cross-platform All-In-One type of library development - shouldn't there
be a wrapper or different set of (same name) files to be included when
going to another platform?
A more modular and heirarchical approach to the library designs is
probably what I'm trying to describe. One that would allow the base
functionality to be there, but with the ability to extend it beyond that
in various ways without touching (ie modifying) the base code. Nothing
new there - been done before in many languages.
The Standard Euphoria Library does seem to be dead, but it's a sound
idea - especially for Windows development. Looking through many files I
see repetition of so many functions and slight variations on functions
(eg. or_all() and or_all_bits() ) - that strikes me as simply a lack of
some further core libraries which we all could benefit from.
What are the benefits of each of the current Windows libraries anyway?
What are the differences? Which Library is the most used? What can be
done to help improve (and/or merge ) the libraries (or preferably one)
Still not an attack, just a discussion from a new Euphoria user who's a
little confused, having come from the C/C++/Java/PHP/ActionScript
world!! :)
|
Not Categorized, Please Help
|
|
