Fredo's plugin checker

[watkins]

Dear Fredo,

When I use your plugin checker it suggests that I do not have the most recent version of cleanup, even though I have installed it. The checker appears to be calling for an earlier version. What's up doc!

---

[Dave R]

In alphanumeric terms 9 comes after 10.

1
10
11
2
3
4
5
6
7
8
9

[cotty]

so Thomthom should change his numbering:
3.1.10 --> 003.0001.0010

[watkins]

It makes more sense to increment 3.1.9 to 3.2.0 (sort of hundreds, tens and units)

[fredo6]

@watkins said:

It makes more sense to increment 3.1.9 to 3.2.0 (sort of hundreds, tens and units)

Actually, this is because I use a letter for the secondary release minor number.
I'll fix that in a next version.

Fredo

[gullfo]

a lot of times a build # is included: 3.1.9.1432 etc but i agree on incrementing the first 3 values although without adding a zero you will ultimately run into this issue with version 10.1.0 etc...

[thomthom]

@watkins said:

It makes more sense to increment 3.1.9 to 3.2.0 (sort of hundreds, tens and units)

Next iteration of 3.1.9 would be 3.1.10 - each number is an independent integer that doesn't overflow to one before. Major.Minor.Revision

[thomthom]

@dave r said:

In alphanumeric terms 9 comes after 10.

1
10
11
2
3
4
5
6
7
8
9

Yeah, that's naive sorting where the numbers are treated as strings instead of the actual number they represent.

@gullfo said:

a lot of times a build # is included: 3.1.9.1432 etc but i agree on incrementing the first 3 values although without adding a zero you will ultimately run into this issue with version 10.1.0 etc...

Zero padding would just be patching up for treating the numbers as strings.

There is no problem dealing with version numbers in a correct way without padding.

major, minor, revision = '3.1.10'.split('.').map { |string| string.to_i }
Then you have integer components of the version string which can easily be sorted and evaluated as greater or lesser than.

[thomthom]

I found that I had forgotten to update the thread which Fredo's checker checks for what the latest version is. It was still saying 3.1.9.

[fredo6]

For info, the next release of LibFredo6 will support both version scheme

• major.minorLetter, like 4.9b (me)
• major.minor.release, like 5.7.10 (thomthom)

Currently it only supports my convention.

Fredo