code comments

[jmo21]

Actually the most annoying ones I find are..

// Fix for bug #196, Fix By Joe Bloggs, 12/12/03

I want to take people outside who do that and beat them about the head with a CVS manual until they know what a repository is used for.

last client co was like that but actually worse eg:

// Fix for bug #196, Fix By Joe Bloggs, 12/12/03
// old code line
.... new code....
// end Fix for bug #196, Fix By Joe Bloggs, 12/12/03

[jmo21]

Current ClientCo. want me to write a comment block at the start of every function with a change history of that function. I've made the point that that's what source control is for, but they haven't changed the policy yet.

last client co did that too

[Moscow Mule]

last client co was like that but actually worse eg:

// Fix for bug #196, Fix By Joe Bloggs, 12/12/03
// old code line
.... new code....
// end Fix for bug #196, Fix By Joe Bloggs, 12/12/03

The sooner we can implement CVS (or indeed Subversion - I don't care) for the iSeries the better.

I once heard a sales line that the product I work on had more lines of code than the the leading competitor. What the sales guy didn't realise was that 50+% of them were commented out bugs....

[VectraMan]

I did once peruse a book all about (apparently) Object Oriented Assembler.

I put it back on the shelf.

No reason at all why you can't do object oriented assembler. You don't need to be able to define types just to be object oriented (although it does make it a bit easier).

In fact, most of the assembler I've ever done has been done inline in C++ functions.