>Changes from 5.0.1 to 5.1.0
>1. The major version of the API is bumped to 3, something that should
> have happened at the 5.0.0 release but didn't.
Just out of curiosity, what changed in the API this time?
What are the benefits of the new API version?
Is this a breaking change, like the one between 4.1 and 4.2?
I ask, because I never really got around to "updating" past 4.1, because of
this API breakage. I have a lot of deployed systems that depend on my
collection of extension libraries and a combination of "It's just too much
work" and "I never got around to it" and "I don't see any benefit" have
kept me from fixing all the source code (*), re-compiling, testing, and
deploying to the myriad of systems that are running all of these libs.
It would take a pretty good reason to get me to do all of that.
(*) Yes (I know you know this, but others reading this may not), the change
from 4.1 to 4.2 required source code changes (not just a recompile).
P.S. It is getting to the point where the libs are esentially tied to a
particular version of the main GAWK program. As such, they aren't
"portable" (in the sense in which I mean that term), so you might as well
just compile them in. That's what I did in the old days (the GAWK 3.x
version of the shared libs thing) - it got to the point where it was more
trouble than it was worth hauling the shared libs around, so I just
compiled them in directly to the main GAWK program. The thing is, I
figured out how to do that back then, but have not taken the time to do the
same thing with the new API. Any pointers on how to do this?
That's the Trump playbook. Every action by Trump or his supporters can
be categorized as one (or more) of:
outrageous, incompetent, or mentally ill.