Re: refactoring when using CVS

[Paul Sander]

>--- Forwarded mail from address@hidden

>>>>>> "David" == Thornley, David <address@hidden> writes:
>David> 
>>> -----Original Message-----
>>> From: Noel Yap [mailto:address@hidden
>>> > Refactoring in C could just as easily leave you with
>>> > a whole lot of
>>> > deleted files and a whole lot of new files.
>>> 
>>> The difference is that as a language, C doesn't demand
>>> such changes (ie renames and moves), while Java does.
>>> 
>David> Yup.  In that respect, I consider Java broken.


>Well, to be absolutely picky Java really *doesn't* care where the source
>files reside.  In fact, there doesn't have to be any correlation between
>the source file name and the resulting .class files.

>It simply makes finding things in the Java source difficult; it also would
>not allow you to do incremental compilation or even figure out the
>dependencies. 

>If you have all of your source in one big pile, you can do a "javac *.java"
>and things should sort themselves out.

Unfortunately, if this is what your build procedure consists of, then
you lose traceability between your sources and shippables, and you can't
assess the impact of any change you make to your source code.  That makes
it really really hard to accomplish the common task of shipping minimal
patches when bugs are found in the product.

>--- End of forwarded message from address@hidden