Comment Re:it's dead jim (Score 1) 54
Not this time. Before I've gone on after a redesign and thought it looked 'odd'. This time I just thought it looked shit
Not this time. Before I've gone on after a redesign and thought it looked 'odd'. This time I just thought it looked shit
Often the comments just end up deliniating sections so I can skip to them easily "// check parameters
For me that's the main reason I comment. I started off as a maintenance programmer and quick often I was looking through the codebase trying to find the procedure (or section of some 600 line behemoth) that I needed to fix. In a case like that I don't want to read 100s of lines of code I have no damn interest in.
The key to these is to keep the comments quite vague.
The other times I comment is to clarify code (quite often you are only allowed to make a specific fix on code that is a clusterf*ck) or to explain why I didn't do something in what seems like the 'obvious' way.
"There are a lot of artists out there whose music I enjoy that I would not have if I had not downloaded their music"
There was no *additional* cost to the manufacturers for the music they 'stole' but there was benefit arising from that in the form of the music and tickets they bought
If you're asking what I think you're asking
let @/=""
I think the idea is that since the / is your search you're setting it to be empty ("")
Looks like we will be bought over and chucked in the bin.
Time to develop those perl/python skills in the long winter evenings...
Any programming language is at its best before it is implemented and used.