aziascreations / pb-utils

A collection of small independent includes for your PureBasic programs that aim to provided some missing and important functionalities.

Heya ! I'm Herwin Bozet

Website • LinkedIn • Twitter

I specialize in minimalistic CLI tools, libraries, self-hosting, electronics and SBCs.

🧰 I develop in PureBasic, Python, C99, C#, JS, PHP, VBA, Java, ...
🏅 Made people's day with Excel Password Remover & Youtube Auto Archiver
🌍 Open to contribute to FOSS in my spare time
✉️ You can hit me up by Email, Twitter, Discord or Libera.Chat _{^{(/msg NibblePoker)}}

Check out the NibblePoker organization on GitHub for more "professional" projects.

pb-utils's Issues

PB SemVer: Tanks, and Another Link Too

Hi @aziascreations,

thanks for publishing this project, and with such a permissive license. I was looking at your SemanticVersioning.pb and I'm very interested in it.

I didn't know that there was already some PB code to deal with SemVer, so I ended up drafting a version of my own for a project I was working on (but currently stalled due to lack of time and loss of motivation). But I'm surely going to need to look at your SemVer version soon.

I though you might like to know about the version I created:

• https://github.com/tajmone/pb-archives-test/blob/source/_butler_/butler-src/butler-mod_dependencies.pbi

It comes as a module, and might need just a few tweaks to work anywhere else (see comments about cross-module Enums).

The module also validates a given SemVer against a constrained version, using some constrain operators:

; A module for checking that dependencies satisfy specific version ranges.
;
; Currently Supports:
; -- Numerical identifiers (only)
; -- Versions with two or more segments (ie: 1.0; 1.0.0; 1.0.0.0; etc.)
; -- Constraint operators:
;    -- "="  --- Strict:        Lock all segements (default)
;    -- "^"  --- Caret:         Lock MAJOR version
;    -- "~"  --- Tilde:         Lock MAJOR and MINOR version
;    -- "~>" --- Twiddle-Wakka: Lock all segements except rightmost

My module doesn't take in consideration pre-release versions when comparing, though (as this would have added to much complications for the time being).

The good thing is that version validation works also with non stricly SemVer version schemes (eg: 2.0.0.1) — it actually works with any number of segments as it will balance segments between the version to validate and the constrain.

I hope it might be useful to you also.