Re: [Alephmodular-devel] Comments on Obsolete code

[Br'fin <br...@ma...>]

I got a nice suggestion from Chris.

I'm now removing all obsolete code. (Generally including calls to a 
function if the function body is completely obsolete) and if anything 
interesting looks like it is getting removed, then I am noting it in 
alepModular/documents/obsolete_gems.txt

-Jeremy Parsons

On Friday, January 3, 2003, at 11:28  AM, Br'fin wrote:

> I just remembered one of the other things I meant to do for 0.3. 
> Removing the obsolete code.
>
> I already snipped out a code block in map_constructors.cpp that was 
> #ifdef'd as NEW_AND_BROKEN. However it occurred to me that while some 
> blocks are just going to be obsolete. Other blocks are going to be 
> obsolete but useful. For instance an obsolete block that specifically 
> refers to M1.
>
> I know all these things will remain in CVS. However, who's going to 
> know these blocks are there to look for at the time when we do start 
> adding M1 support? Leave them in the code? Remove them anyways but add 
> an extra note in the CVS log?
>
> And as should be expected, I do have my eyes on removing the Valkyrie 
> support code as part of obsolete code removal.
>
> -Jeremy Parsons
>