info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: refactoring when using CVS


From: Greg A. Woods
Subject: Re: refactoring when using CVS
Date: Thu, 21 Feb 2002 13:27:42 -0500 (EST)

[ On Thursday, February 21, 2002 at 05:46:41 (-0800), Noel Yap wrote: ]
> Subject: Re: refactoring when using CVS
>
> --- "Greg A. Woods" <address@hidden> wrote:
> > [ On Wednesday, February 20, 2002 at 13:19:22
> > (-0800), Noel Yap wrote: ]
> > > Subject: Re: refactoring when using CVS
> > >
> > > The difference is that as a language, C doesn't
> > demand
> > > such changes (ie renames and moves), while Java
> > does.
> > 
> > That's really totally and completely irrelevant.
> 
> In C, you can separate the actions of changing code
> for refactoring purposes and moving/renaming files (ie
> you can do it in two checkins).  In Java, assuming you
> don't want to break the compile, you can't.

That's really totally and completely irrelevant.

So Java is worse than C.  We knew that already.  It takes more man-hours
to write, results in more lines of code, runs on fewer platforms,
generally runs a lot slower, sometimes even slower than the equivalent
perl code, isn't as secure as its proponents would have us believe, and
lastly and "leastly" most/many/all? of the common so-called java
development environments make attrocious use of the filesystem.  It's
all totally irrelevant to what I said.

> Haven't you encouraged doing moves/renames as a
> separate checkin from code changes?  Or have I
> misunderstood?

Your missing the point so completely I don't even know where to try to
pull to get you back on track.

-- 
                                                                Greg A. Woods

+1 416 218-0098;  <address@hidden>;  <address@hidden>;  <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]