On 1/10/2011 6:55 PM, Leo Butler wrote:
>
> On Mon, 10 Jan 2011, Richard Fateman wrote:
>
> Any decent editor, like emacs, can display comments in a form in which they do
> < not
> < intrude in the code (say in a different font and/or color), but are easily
> < available.
>
> The issue is not so much hiding comments, it is this: what happens when
> Y alters X's signed code with its pretty comments. Does Y leave X's
> comments, and add more?
Ordinarily, yes.
> delete X's and add more?
If X's comments are no longer appropriate, that is occasionally
possible, but hazardous
since Y might be wrong, in which case Z might fix both the comments and
the code.
> The dilemma faced by
> a graffiti artist, created by not using the appropriate tool: an rcs.
>
>
> < Maybe
> < I'm old fashioned, but I find opening the CVS log at sourceforge to be a pain.
>
> It's CTRL-xvl in emacs.
"no fileset is available here."
I do not ordinarily download every new source directory, nor do I
download CVS.
> Even better, you can check out the previous
> revisions and see the changes yourself, all with half-a-dozen key
> strokes.
If a source file is to be readable as a document describing a program,
it should
be possible to print it out and read it. I would hesitate to read a
book which could
only be read on-line and which would not make sense unless you clicked on
links. Such a document/web page DOES make sense in some contexts,
where you are interacting with some neat web application.
I just don't think of program listings that way. Usually.
RJF