Re: C++ ready

On Sun, 2002-10-13 at 12:43, Adrian Chadd wrote:
> On Sat, Oct 12, 2002, Robert Collins wrote:
> > Right, I now have a C++ ready core of squid - everything in the src/
> > directory and all it's subdirs builds and runs cleanly with C++.
> >
> > So, can I bring it across (with or without the new storeGetPublic
> > calls)?
> >
>
> Well, you're renaming all the files in src/ to .cc, right?

And creating headers for some of the tightly coupled stuff.

> I think we should give this a go, but I'm not sure if we should keep
> it in the current repository. If we're renaming all the files then
> we'll be losing quite a bit of history unless we want to go down
> the repo copy path - and I'm not sure we should do it for everything
> in src/ .

The history is still there, jsut across the .c->.cc boundary. IMO that's
not an issue (you can still cvs annotate the .c files :}.

> So, here's my question to squid-dev: should we look at creating a squid3
> CVS repo, grant the same people access to it, and continue refactoring in
> there?

IMO no - there is a *LOT* of code not changing. lib/* hasn't been
touched as yet (given that it's already quite well separated out, I saw
no immediate benefit or need there). snmplib/* likewise. helpers/*
hasn't been touched, and thats something like 30-40% of our code.

Rob