Re: [Firebird-devel] Obsolete files in Vulcan.

[Nando D. <na...@de...>]

Roman,

>> You made a point. All files that we deleted, including the whole directory
>> structures, are still available at SF, thus nothing is lost really.

RR> And what happens if SF.net crashes?

Are you seriously suggesting to use commented source code as a backup
mechanism? ;-)

RR> Or we decide to move to some other place and Subversion, for example?

...or as a migration tool (BTW, CVS -> SVN migration tools exist)? ;-)

RR> And where should new people learn that this
RR> code ever existed in the CVS?

This is a fine point, although I have heard people here saying that if
the code doesn't work and cannot be made to work then it's not
something you should show to newcomers as an example. Furthermore,
experience says that code kept around "just in case" tends to become
quickly out of date (expecially if it's not part of the build) and
effectively unusable when the case happens.

RR> So, I think that what Jim said makes sense, though those directories should
RR> move away from the src/ directory, so nobody is confused that this code
RR> participates in build.

this might apply to whole files, but it doesn't apply to parts of
files (which are perhaps not in topic for this discussion, I reckon).

Ciao
-- 
Nando Dessena
http://www.flamerobin.org