Libmarpa versioning will not be visible to most of Marpa's users. In
particularly, if you use Libmarpa only through its Perl interfaces,
you'll probably never notice it.
But for those thinking of using Marpa's C library, it may be
significant, so I wanted to toss this out for comment and discussion.
Jean-Damien has been creating shared libraries from Libmarpa, and
currently they are not versioned -- they're all 0.0.0. This is not
adequate and forces me to decide on a versioning scheme. Libmarpa's
versioning is not tied to that of Marpa::R2 (although Marpa::R2 is very
very fussy about which version of Libmarpa it is using.)
At this point I intend to use a scheme currently in use mainly for
security libraries, where the version is of the form MAJOR.MINOR.MICRO,
but MINOR and MICRO are always zero. This makes every change a major
version change, which means that in most environments no version will be
treated as compatible with any other. In Marpa's case the reason for
this ultra-cautious style is that development is aggressive, but the
software is extremely complex and interactions are complex. An upgrade
discipline that simply "drops in" changes seems to me over-aggressive in
this context. I'll admit I am inclined, if I must err, to do so on the
cautious side.
My current inclination is that the next Libmarpa version will be 3.0.0
and all subsequent ones will be of the form MAJOR.0.0. (Note that this
three (3) has nothing to do with any plans for a Marpa::R3).
Your comments, advice, etc., are welcome.
--
You received this message because you are subscribed to the Google Groups "marpa
parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
