Re: DUB 0.9.22 released
On 25/09/14 21:38, Ben Boeckel via Digitalmars-d-announce wrote:
What about 1.2.3.x? How does dub handle letters in version numbers?
Maybe 1.2.3.0w would be viable ('w' for 'wrap').
I don't think that's allowed. Dub's following this versioning scheme:
http://semver.org/
--
/Jacob Carlborg
Re: DUB 0.9.22 released
On Thursday, 25 September 2014 at 19:38:47 UTC, Ben Boeckel via
Digitalmars-d-announce wrote:
What about 1.2.3.x? How does dub handle letters in version
numbers?
Maybe 1.2.3.0w would be viable ('w' for 'wrap').
1.2.3.x is an invalid version number. Only 3 group numbers are
allowed [1]. Though you could use prerelease and/or build
suffixes (1.2.3-0w / 1.2.3+0w).
[1] - www.semver.org
Re: Mono-D v2.4.9 - Parser fixes
On Thursday, 25 September 2014 at 22:02:14 UTC, Piotrek wrote: I was shocked how smoothly Mono-D works compared to DDT. Well maybe, but there's a lot of performance improvement required -- just open std.traits and see what lags there are due to its attempts to highlight usages of the currently selected symbol identifier :/ On linux it wasn't one click install though. I had to compile Monodevelop myself to get the plugin working. And to be fair I didn't check DDT for some time now. Instructions and a precompiled distro-independent bundle are given this time, though! In short, Mono-D FTW! Alexander, thanks for your great contribution. Piotrek Thanks - and don't forget to file issue reports on github instead of raging silently, please! :-D
Re: DUB 0.9.22 released
On Friday, 26 September 2014 at 06:29:21 UTC, Dragos Carp wrote: Though you could use prerelease and/or build suffixes (1.2.3-0w / 1.2.3+0w). These are very close to what I would like to see. Though, if I understand correctly, build suffix wouldn't work, as for example 1.2.3+0w and 1.2.3+1w would be treated as equal: Build metadata SHOULD be ignored when determining version precedence. Thus two versions that differ only in the build metadata, have the same precedence. (semver.org) I guess that prerelease suffixes would do the trick. The only problem is conceptual: A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version. (semver.org)
Re: DUB 0.9.22 released
On Friday, 26 September 2014 at 08:37:12 UTC, tn wrote: On Friday, 26 September 2014 at 06:29:21 UTC, Dragos Carp wrote: Though you could use prerelease and/or build suffixes (1.2.3-0w / 1.2.3+0w). These are very close to what I would like to see. Though, if I understand correctly, build suffix wouldn't work, as for example 1.2.3+0w and 1.2.3+1w would be treated as equal: Build metadata SHOULD be ignored when determining version precedence. Thus two versions that differ only in the build metadata, have the same precedence. (semver.org) I guess that prerelease suffixes would do the trick. The only problem is conceptual: A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version. (semver.org) In semver library [1], the differences in build suffixes are a) right ordered (defined sort order) and not equal, and b) considered compatible. a) SemVer(1.2.3+w.9) SemVer(1.2.3+w.10) SemVer(1.2.3+w.9) != SemVer(1.2.3+w.10) b) SemVer(1.2.3+w.9).satisfies(SemVerRange(1.2.3)) SemVer(1.2.3+w.10).satisfies(SemVerRange(1.2.3)) SemVer(1.2.3+w.9).differAt(SemVer(1.0.0+w.10)) == VersionPart.BUILD [1] http://code.dlang.org/packages/semver
Re: Daemonize v0.1 - simple way to create cross-platform daemons
Excellent library, thank you very much for sharing it. I was about to start my own when I ran into it :)
Re: Daemonize v0.1 - simple way to create cross-platform daemons
On 8/31/14, 4:27 AM, NCrashed wrote: Finally I've finished library for wrapping applications into daemons or services (Windows). The library hides platform-specific boilerplate behind compile-time API: [snip] I completely missed this. Has it been reddited? -- Andrei
