News for hackers. Stuff that matters.
Re:Poll: What kind of tool do you use to write code? by RyanZAG on Saturday December 15, 2012 @02:32PM (#4926070)
Meta+Click on a function to take you to that function's implementation is easily one of the most production enhancing benefits of an IDE in larger code bases.

Also, don't knock the ability of some IDEs to show function documentation on mouseover - this can save a huge amount of time in reading API docs.

Re:Poll: What kind of tool do you use to write code? by holri on Saturday December 15, 2012 @02:50PM (#4926134)
emacs can do this too and gives you complete control over everything. You can even go to the lisp source of the editor commands very easyly.
Re:Poll: What kind of tool do you use to write code? by carbocation on Saturday December 15, 2012 @03:37PM (#4926266)
Your point and the point of the comment to which you are replying seem to suggest a 3rd space.

(1) There are IDEs, which include things such as build automation, debuggers, function lookups, etc. (2) There are text editors which maybe give you syntax highlighting.

I don't think I'm saying anything novel by suggesting that there is also an in-between: something that provides syntax highlighting, function lookups, etc., but which doesn't try to build your project for you.

You can use emacs like this, and you can use an IDE like this. So, many people voting for text editor and many voting for IDE may actually mean something more like this.

Re:Poll: What kind of tool do you use to write code? by huhtenberg on Saturday December 15, 2012 @03:11PM (#4926188)
ctags followed by Ctrl-T in vim does the exact same thing.
Re:Poll: What kind of tool do you use to write code? by mercurial on Saturday December 15, 2012 @03:37PM (#4926268)
Including functions from an external libraries?
Re:Poll: What kind of tool do you use to write code? by chameco on Saturday December 15, 2012 @03:46PM (#4926290)
Yes. You can create a tags file for any header file, no matter it's origin. I like to keep mine (for boost, GL, SDL, etc) in ~/.vim/tags and set that as my default tag directory, then use a plugin (Easytags) to auto-update tags for the current source file. That + Supertab + omnicomplete = win.