I wrote this in the heise forum because I'm
considering an interface for Smalltalk, but
having only a C++ interface is simply making
the whole stuff much more complicated -
comparing against the possible API stuff of
MS Office (and I think its fair to compare OO
against MSOffice - even if OO is platform
independent - most of the users of OO are
also MS Windows users ...)
Designing a C interface may be more difficult
for the developers, but it will be much easier
for the users of such an interface.
Go away from language bindings at the first
level API and make a totally language independent
API with a defined call structure for C.
My comparisions in that posting were done with
ObjectOriented databases because I noticed the
same problems there - especially since Java
has grown in popularity.
Marten
I just noticed somebody else making a similar argument:
http://www.heise.de/newsticker/foren/go.shtml?read=1&msg_id=8172098&forum_id=80089
That writer mentions that providing the C interface
first is the way to go; other languages' interfaces
are much easier to base on a C interface than on
a C++ interface. This is certainly something I've
heard in other contexts, too.
- Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
