Macro explanation?

[Randy Kramer]

On Monday 12 November 2007 01:54 pm, Joachim Lous wrote:
> > I may do that, but probably not on my first pass through the code (which 
is
> > still where I am).
> 
> Ah, but how will you remember next time what was difficult? :-)

Good question.  But I'm certainly not ready to put comments in the code.  At 
most I'd do something like add double question marks (indicating puzzlement, 
surprise, or whatever) as comments.  And, if I don't commit those comments, 
then when I do a cvs update, I'll lose them.

I guess I could keep a personal copy of the code with my marks in, and at some 
point that is probably what I'll do, but for now I haven't seen much worth 
the effort.

Hmm, I guess that's the better answer--so far I haven't seen much (in the 
comments) that puzzles me.  And, as far as the code goes, there's an awful 
lot that looks greek to me, but I'm assuming I'll gradually get a handle on 
that.

I do wonder sometimes what is the proper balance between newbie and non-newbie 
comments in the sense that, it would be nice if a well intentioned Jay Random 
User could have a hope of fixing some problem he sees.  But, I think the 
reality is (especially in something as complicated or more complicated than 
nedit), it takes weeks or (much) longer for even an experienced C programmer 
to know enough about the code base to make a change.

Anyway, if I do find problem comments, I'll try to do something about it.  

I guess another factor is that, at least for the moment, I'm taking comments 
at face value--I have no basis to recognize a misleading or incorrect 
comment.  (But, when I do, like I say, I'll try to do something about it.  
Maybe at first it will just be a post to the list.)

Randy Kramer