Perhaps you didn't understand my point though. I'm not suggesting that
you code with glib/GObject. But more, that if there was a C++ binding
of libInstPatch, that you would use that instead of forking your own
branch of it.
At the moment I'd like to have the freedom to modify the loader code, so it's either porting it to C++ (no big work, we're talking about just a couple of files) or using glib/GObject. In the future, who knows.
Yes "vamp off" was probably left over from my initial
frustration and it really depends on what you do with the code that
determines whether that has any validity or not.
I'm sorry, but I fail to see how any use I may decide to make of your code would be "vamping off". Quoting from the comment at the beginning of every libInstPatch source file:
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public License
* as published by the Free Software Foundation; version
2.1
* of the License only.
*
* This library is distributed in the hope that it will be useful, [...]
So if I follow the terms of the LGPL, am I not free (both legally and morally) to use the code in any way I deem useful? Licensing code under the LGPL is giving others explicit permission to take that code and modify it; otherwise a no-derivatives license would be more appropriate.
I strongly reject the notion that I might be doing something wrong by modifying your code, depending on the use I make of it.
If you were using a libInstPatch C++ binding though, it would help the
development of libInstPatch indirectly (regardless if you had any part
to play in the C++ binding). My frustration comes from the fact that
libInstPatch is a library, and is a library so that others can use it.
And using it I am. I fail to see why some uses are more correct than others.
So question: if there was a C++ binding, would you use it?
Perhaps in the future; I would have to consider it because I like to have as few dependencies as possible. It depends on what part of libInstPatch functionality I would need.
As I've stated before, I completely respect your choice of programming
platform and don't particularly care to force anyone to use
glib/GObject. I've also thought about moving away from it at times.
But the accessibility nature of it, has kept me using it. If there ever
comes a time to port libInstPatch/Swami development, now is not that
time, since its not even seen an official release yet.
Your decision and I wouldn't dream of suggesting otherwise.