On 11/25/2009 03:12 PM, John Plevyak wrote:
Good point. So non-virtual functions which would imply wrapper objects
for internal objects with virtual functions. I wonder if there are any
tools to automate that.
Sigh. This is getting complicated. C++ is a pain. Makes me think
the C API isn't so bad.
An important goal for our first ASF release ("v2.0") needs to be to
freeze anything in APIs and ABIs that would otherwise break backward
compatibility. Within the v2 release cycles, we can not break APIs or
ABIs (IMO at least). Since we have no compatibility issues to deal with
right now (since there has been no release yet :), now is the time to
figure out as much as we can for changes that could break compatibility.
This should include changes in the core too, like the cache dirent
changes John is doing (now is definitely the time to do that, so people
don't have to worry about nuking their caches when upgrading to a newer
TS relase).
So, lets keep the discussions open. I'd urge that we start Confluence
Wiki pages for all major code changes that would change internals like
this. I'll start one for the Remap plugin APIs once I get the time to
work on that (hopefully in a week).
Cheers,
-- Leif
