If developer assure that his library works with the current compiler then is enough. Otherwise will be too much work and useless for developer.
The user have two alternatives: - to keep an archived version of the package used to develop his application (this is mandatory) - to migrate his application to the newest package. For me as a user is fair enough. Vasi On Dec 25, 12:45 am, Oliver Seitz <[email protected]> wrote: > > This is one small thing that I don't > > feel is important, although some > > may say it is. I think it is not important since I'm sure > > all my files > > will work with the latest stable compiler, whatever that > > may be. > > It is the other way round: That statement should inform the user about which > compiler is the *oldest* the lib is believed to work on. > > Greets, > Kiste -- 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.
