I just made an ABI break.
It's a teeny tiny one, and as a signature fix it comes under the warning
on the main /4.0/ web page.
The fix is going in (it has to), but I am debating whether this should
cue a bump in java-gnome's API version number.
ie, we are [quite deliberately] set up as
epoch.api.version
right now. So the next release will either be
4.0.13
or
4.1.1
The glitch in question is that we had gunichar registered as Java char,
not Java int. So, surprise, splat. The method that is changing is
TextIter's getChar(), now returning int.
No one with a widely distributed libre codebase is using it, so I don't
feel compelled to bump java-gnome's API version number, but I thought
I'd let you know I was thinking about it.
[if it wasn't for the fact that StringBuffer's append(int) doesn't
append the codepoint but instead does a Integer.toString(int), this
would have been transparent. Alas]
If I do, I'll remove all the @deprecated stuff at the same time.
AfC
Sydney
--
Andrew Frederick Cowie
Operational Dynamics is an operations and engineering consultancy
focusing on IT strategy, organizational architecture, systems
review, and effective procedures for change management: enabling
successful deployment of mission critical information technology in
enterprises, worldwide.
http://www.operationaldynamics.com/
Sydney New York Toronto London
|
