Hi Joep, I agree this information isn't that useful now (ever ?). I guess this compiler version information could be at global level. We could simply remove it from source files, and mention in CHANGELOG a version used for libraries (as it is already the case). By providing jallib-pack, compiler included, users knows what to use.
Cheers, Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org 2009/9/3 Joep Suijs <[email protected]> > > Hi Guys, > > Each file we maintain has the minimal compiler version in it. It takes > some effort to maintain and has a risk of providing faulty > information. > At the time, the compiler version in each file seemed usefull, but I > now think it is not. We provide a package of files that works on the > latest stable version of the compiler (which is also provided). > So I suggest we supply the compiler version on which the files are > tested and not a minimal version for each file. > > How? Well, we could put of course put it in each file (and have the > buildbot or some other script to check for the right version or even > maintain it). Or maybe remove each from each source and at some other > place? > > Joep > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
