Jeremy Ruston wrote:
>
> So, yes, we could expose it as a filter operator. Perhaps it should be
> done as part of a broader effort to add comparison operators.
>
That, including comparison ops, would be most excellent!
Should I put up an issue?
<:-)
--
You received this message because you
Hi Mat
> On 2 Jul 2019, at 20:06, Mat wrote:
>
> But I'm thinking that the core has a built in version comparison mechanism
> used in import. Is it possible to tap into this perhaps?
The core does indeed have a function to compare “major.minor.revision” format
version numbers:
Thank you Mark.
The problem is that it has to be general enough to compare any two plugins
not only the core. But the two plugins *are* the same plugin, just
different versions. And it is not sure that the plugins follow the x.y.z
format.
Waiting until 5.1.20 is not a problem though.
But
I can see how you can do it with two filter loops, and a slight cheat.
Maybe two cheats.
The first cheat is that for most revisions, only the last part of the
dotted notation is significant (e.g. 5.1.*20 -- *only the last dotted
number has change for the last 4 (?) years).
The 2nd cheat is
4 matches
Mail list logo
