On 03.04.2009 18:21, Brian Aker wrote:
> Hi!
>
> I got pinged about this and was asked to share my thoughts.
>
> In Drizzle we have moved toward picking classes which we are
> identifying as API. This is a slow process and has required us to
> rethink some classes in order to provide what we feel will be a good
> long term API (and we are not finished with it either). The class
> structure in MySQL is more of a "public structure with functions" then
> any sort of real API. I would think twice before just opening up all
> of these to the world.
Also I don't really want to open/install all headers, it just looks like most
of them are required to build a plugin at the moment and I a) was too lazy;
b) did no feel competent enough; to choose the ones that should not
be installed, leaving it up to your consideration.
If you don't want to install some of them AND it doesn't affect the plugin build process -
fine, I don't care.
> Opening up the class headers means you are creating a pact between you
> and your developer base. You are saying "this is an API, we promise to
> inform you of changes, and to not make them lightly". Is this where
> the MySQL codebase is today?
I'm definitely not the right person to answer such questions.
--
Wbr,
Antony Dovgal
