On Dec 18, 4:16 am, Roman Roelofsen
wrote:
> IMHO, no. This is the whole problem. Library users will mostly care
> about the runtime. It doesn't help at all if your code compiles, maybe
> in isolated pieces, but everything blows up at runtime. For example, I
> never had problems compiling against
> Talking of semantics, do you think the one I enumerated would work?
> I'll certainly try to implement this concept, but I have many other
> projects on the table right now, so it might take a while before I
> start working on it.
Yes, it looks good. The key thing is that all users/developers agr
On Dec 17, 3:13 am, Roman Roelofsen
wrote:
> Dealing with version numbers at build time is quite easy with tool
> like Maven. The important thing is that everyone agrees on the same
> version semantics (great summary [1]). Putting some more tooling
> around this should be a good idea, yes.
Talki
On Dec 17, 3:11 am, Laurent PETIT wrote:
> Isn't this the ideal that clojure and libraries are almost more or less
> already following ?
Yes it is, but that's because the maintainers are very disciplined and
professional people. Not everybody follow this scheme properly and
even the best of us ca
completely incompatible with OSGi. If we could solve this, Clojure
would instantly get multi version support.
Cheers,
Roman
[1] http://www.osgi.org/blog/2009/12/versions.html
2009/12/16 Nicolas Buduroi :
> Hi, on the CommonJS Google Group there was a discussion on semantic
> versioning, a
Isn't this the ideal that clojure and libraries are almost more or less
already following ?
2009/12/16 Nicolas Buduroi
> Hi, on the CommonJS Google Group there was a discussion on semantic
> versioning, a formalization of the concept of properly using a common
> version
s/thinking/think/
On Dec 16, 2:56 pm, Nicolas Buduroi wrote:
> Hi, on the CommonJS Google Group there was a discussion on semantic
> versioning, a formalization of the concept of properly using a common
> version number scheme (Major.Minor.Patch) for libraries.
>
> http://semver.o
Hi, on the CommonJS Google Group there was a discussion on semantic
versioning, a formalization of the concept of properly using a common
version number scheme (Major.Minor.Patch) for libraries.
http://semver.org/
I think it would be especially easy to enforce a simple version of
this system in
