Carlos,

> JW> Actually, I do have others that are quite helpful at times who
> demonstrate
> JW> significant abilities to get inside the IBO code base and assist.
>
> I'm glad to know that!
>
> JW> I will do my best to work with Geoff so that there isn't an unecessary
> JW> branch generated in the IBO code base.
>
> Very good. As a developer, I understand that sometimes, creating
> private branches are necessary. But when I need to fix/enhance
> something in the source of a third party product, I like to do it in a
> way that can be easily integrated in the "main tree" (because I
> usually send my changes to the component's author). This is good for
> both sides, since the author and community can benefit of the
> enhancements, and it makes easier for me to keep in sync with all
> newest versions, since I do not have to compare/sync/test all the
> private changes every time a a new version is out.

Yes, exactly, this is most appreciated by me when others do this. There are
many instances where people have asked me to make little changes in IBO so
that they can have their own independant sub-classes so that their code and
my code can remain compartmentalized and they can easily stay with future
versions of IBO and not have to perpetuate the hacks they have made to my
sources. Most of the time it is making a static method virtual or moving
something from private to protected.

Thanks,
Jason Wharton