>> When making changes to source code, do people really think of it as >lines >of characters, as printed on paper or displayed on screen, or >do they think of it in more abstract terms, of expressions, statements?
What do people think about when making changes to other forms of text? I don't see why code should be any different from, say, a novel or a technical paper. >The first one, the //TODO:. I do similar things. >One feature of editors/ide-s that I continually use and (want >to use if it isn't there) is the bookmarking feature allowing >me to lines of code in the same file. This is great when in >the middle of refactoring, since then you can hit the 'next >bookmark' or 'previous bookmark' key combos quickly. The fact >that these can be saved between editing sessions using my ide >is great. I've never found bookmarking systems particularly useful - I just remember the places. : I'm the same with books, I just rmemeber the page, I don't use markers. (Though clearly bookmarking systems have a useful archiving role, but this doesn't seem reelevant for the immediacy of changing code) L. ---------------------------------------------------------------------- PPIG Discuss List (discuss@ppig.org) Discuss admin: http://limitlessmail.net/mailman/listinfo/discuss Announce admin: http://limitlessmail.net/mailman/listinfo/announce PPIG Discuss archive: http://www.mail-archive.com/discuss%40ppig.org/
