Markus Werle wrote:
Joel de Guzman wrote:
Markus Werle wrote: [...]
2. Spirit-2b is a break-all-of-the-interface-change. I understand that some people prefer it to be in directory spirit2 and you prefer it to be merged with spirit-1. I respect your opinion and your freedom but I strongly disagree. Right now, a developer can update/enhance/improve his library anyway he sees fit without further review.
That is exactly my point. I do not regard Spirit-2 as update, enhancement or improvement. I see it as something completely new and different. OK, yes, it is an enhancement and improvement, but not in an evolutionary sense. I do not see any evolution, I see big changes. There's no brick on the other anymore.
AFAIK, there's no rule that prevents an author from completely rewriting his library either. Such things are common when moving to a major version.
If you or anyone else want to change the rules,
I thought that the rules already disallow the change of 90% of the interface at once. I thought that the boost community was rather conservative regarding interface changes.
I am not aware of such a rule. I've seen major changes happen. Yet, we took great pains in ensuring that the old headers are kept intact (100% backward compatibility). We made sure that the user can be able to migrate at her own pace without panic. That was a must. Many already rely on Spirit 1.8.x codebase and we do not want to cause the slightest disruption ever. Even Hartmut Kaiser's (a major Spirit developer) wave project still relies on Spirit 1.8.x.
Are there any tools to measure code distances? Or should we write on based on Spirit-2?
[...] Spirit-1 is *NOT* deprecated. Only the old headers are deprecated.
Can you write this sentence into the main html page Introduction chapter of the docs?
Definitely. Regards, -- Joel de Guzman http://www.boostpro.com http://spirit.sf.net