Skip to main content

Timeline for ASCII Turtle Graphics

Current License: CC BY-SA 3.0

6 events
when toggle format what by license comment
Dec 31, 2014 at 22:56 comment added Steve Midgley @Mat'sMug Totally true for Java - which to be fair was the OP's reference language. But in other languages, such a comment (IMO) can be handy. I write a lot in Ruby and Python and my editor (Sublime) doesn't tooltip the bottom end block. Agree that refactor makes sense for long methods but long modules or classes are inevitable (again IMO).
Dec 31, 2014 at 20:43 comment added Mathieu Guindon @steve in C# / Visual Studio, when you place the caret on a scope-ending brace and the opening brace is off the screen, a tooltip shows the line of code that opens the scope. I'd be surprised that no Java IDE does that. Also if your scopes are too large and/or confusingly nested, perhaps there's a refactoring opportunity being missed? // end of class xyz is noise if you have 1 class per code file.
Dec 31, 2014 at 20:39 comment added Steve Midgley I often put comments like // class Main at the end of classes or long methods where the top and the bottom of the method are usually off-screen from each other. It helps keep track of which end block is which. So I don't think it's sound general advice to say never put a comment on the end of a block of code. Otherwise I agree with everyone's input that comments should document why and not what.
Dec 31, 2014 at 19:33 comment added Jeff Clayton When you are working for a company, you will do well to comment properly. Make your code readable, so commenting is not always needed, but because more than one user edits, effective commentation is necessary. Don't overdo, but assume a programmer will have to work with your code later who has not seen it before. It will also help you get jobs to have it...
Dec 31, 2014 at 18:45 comment added Eric Stein @Hosch250 No, that's not what he's saying. Comments are sometimes necessary. They should explain the reason an implementation decision was made so that the next person to edit the code understands something that would otherwise be confusing.
Dec 31, 2014 at 18:23 history answered Mathieu Guindon CC BY-SA 3.0