10.08.2014 14:10, Jim Starkey wrote: > It is a fool's errand to try to build a OO interface that is call compatible > across a wide range of OO languages. If anyone is in doubt, look at > Objective-C and weep.
If this is found being impossible (I'm not deeply involved, so I don't have a strongly argumented opinion yet), then we have [at least] three questions to answer: 1) Do we keep the existing OO Y-valve API for internal purposes? E.g. for engine plugins or for remote->engine calls. The same issues apply but we can expect virtually zero practical risks here (I doubt we'll be writing some parts of the server in FreePacal or Lua). Maybe some interfaces could be simplified in this case. 2) Do we offer the existing OO Y-valve API to other C++ users? It has to be public and limitations (including binding issues) have to be documented. 3) Do we keep using the legacy ISC API as the "plain C" wrapper for non-C++ users or invent a better replacement? Dmitry ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
