Re: [Ctool-develop] using ctool as a library

[Stefan S. <se...@sy...>]

Shaun Flisakowski wrote:
> 
> On Friday, August 1, 2003, at 10:39  AM, Stefan Seefeld wrote:
> 
>> Shaun Flisakowski wrote:
>>
>>> Stefan,
>>> Rather than send a huge patch like this you could just become a ctool 
>>> developer so you can use cvs also; for a large change it could go in 
>>> on a branch first to be looked over by concerned parties. I'll just 
>>> need your sourceforge username to add you.
>>
>>
>> I'm known as 'stefan' there.
> 
> 
> Great - you are now a developer.

thanks a lot. I hope I'll make good use of that priviledge and not
putting anybody in danger :-)

> As I mentioned in my previous email, we should try to maintain the old 
> API also (redirecting it to the PrintTraversal in this case), at least 
> for a few releases.

yes. Once the PrintTraversal is debugged, we could keep all the 
individual 'print' methods and 'operator <<' and implement them via
the PrintTraversal methods. That way the interface is preserved, without
any unnecessary code duplication.

>> ok, fine. I'll be on vacation starting today for two weeks, but I'm
>> eager to work on this tool. Please let me know whether you have 
>> anything such as a commit policy. Besides dsicussing possible changes
>> before applying them, do you want to review the actual patches ? Etc.
>> Just to avoid later frustrations...
> 
> 
> I don't yet.  There was only one other ctool developer at the moment, 
> and we were just sort of working it out. He's actually working on some 
> larger open-source tool which is using ctool as a component.

sounds familiar :-)

> I want to hear about larger changes, but I can see the diffs in CVS if 
> I'm just given a list of files.  I don't need to be informed of every 
> bug fix.

ok. Let's see how it works out. Now I'm off for two weeks.
See you...

Stefan