Yes, I'd like to start committing new Annotation parsing code. Problem is, of course, is if clients out there were using the Unknown attribute to gain access to annotations, adding in true Annotation support will cause their code to fail, as Annotations will no longer be Unknown. Things will still compile as is, just not run as expected.
Have you considered adding a new method for accessing annotations?
Code calling the old method would get "Unknown" nodes returned, and new code would get the real Annotations. And the old method could be marked as deprecated.
Regards,
Simon
Yes, we could create Visitor15 interfaces, et. al. But then
*puke* ;)
we live with that mess forever. I'm game for whatever folks agree on, though.
Well ...I'd say let's keep a maintenance branch for a while (which is backwards compatible) but let's not restrict ourselves on trunk.
WDYT?
cheers -- Torsten
signature.asc
Description: OpenPGP digital signature
