[gephex-devel] 0.5 type system -> C++?

[Martin Bayer]

> ~  Disadvantages:
> ~     * C plugins and plugins in other languages not directly possible

1. The only implementation languages of gephex plugins are c and c++ at 
the moment. The only reasons for our c plugins were

- the default language is c
- compile time

2. I don't know of any successful attempt of using a different language. 
I tried embedding the mzscheme interpreter in a plugin. I failed cause 
of an unrelated weaknesses in the old plugin api. But a c or c++ api 
wouldn't change much of the needed code.

> ~     * Compiler dependent plugins (only plugins that are compiled
> ~        with a "compatible" compiler can be loaded)

This should be only a problem with the win32 platform. And at the moment 
we don't even support cygwin or mingw.

Loosing the possibility of mixing binaries from gcc and msvc on the 
windows platform is bad. But i my opinion the advantages overbalance 
this negative issue.

The gephex plugin api is not and will not be a interproject plugin api. 
  The design process of the 0.4 and later the 0.5 api was focused on abi 
and api compability issues. We should design our new plugin api for our 
needs while increasing our efforts in supporting the interproject apis 
like frei0r, livido and freeframe.


I opt for rediscussing once again the c++ plugin interface issue. :)

Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.gephex.org/pipermail/gephex-devel/attachments/20041121/f70e7c7f/signature.bin