I've tried a number of open source IDE's. I cannot comment on closed source products. However, I have settled with the Eclipse CDT. I used to use Gentoo Linux but found that Ubuntu gives an almost 'trouble-free' Linux experience. On Ubuntu the Eclipse CDT runs like a charm. I highly recommend it, and cannot see any reason to use any other. It also has a native Java development environment, if you are so inclined, and is being adapted to other languages.
--random
Linux C++ IDE??
Quote:Original post by aCynic2
Emacs + gcc == purity.
jed is also a nice editor that provides a link to gcc, color syntax highlighting, etc...
It's just that emacs can do EVERYTHING you need.
Where's your debugger?
I like kate/kwrite.
And with the text completion plugin you have minimal and good enough word-completion facility (working exactly like the vi-completion).
Other tools I've been using are gdb(, ddd), valgrind, Krazy2 (automatic, plugable code-checker of KDE4-Project).
And with the text completion plugin you have minimal and good enough word-completion facility (working exactly like the vi-completion).
Other tools I've been using are gdb(, ddd), valgrind, Krazy2 (automatic, plugable code-checker of KDE4-Project).
I have to admit that I do supplement Eclipse with Kate because it is so easy to edit with. One of the drawbacks of Eclipse (maybe I don't know how to use it properly) is the editing of a single file. Doing things like find/replace etc. Kate is easier for this. Eclipse has a very powerful feature called 'refactor/rename' which will parse everything in the project, but sometimes that is too much power for me, and sometimes the refactoring cannot be safely done across files.
--random
--random
Any specific reason you *need* an IDE.
For most things I just use either Gedit or Vim to write source code, and I compile with the gcc from the command line. If I ever need some overly specific compile configuration, or I need to link to more than a few libraries, I just use a makefile.
Personally, I think most IDE's are far too over-bloated and just downright unnecessary for the most part. I mean you have your source code, and then you have the compiler -> compile the source code. Must you really have another piece of software standing in the middle?
For most things I just use either Gedit or Vim to write source code, and I compile with the gcc from the command line. If I ever need some overly specific compile configuration, or I need to link to more than a few libraries, I just use a makefile.
Personally, I think most IDE's are far too over-bloated and just downright unnecessary for the most part. I mean you have your source code, and then you have the compiler -> compile the source code. Must you really have another piece of software standing in the middle?
Quote:Original post by Vuk Samotnjak
Any specific reason you *need* an IDE.
For most things I just use either Gedit or Vim to write source code, and I compile with the gcc from the command line. If I ever need some overly specific compile configuration, or I need to link to more than a few libraries, I just use a makefile.
Personally, I think most IDE's are far too over-bloated and just downright unnecessary for the most part. I mean you have your source code, and then you have the compiler -> compile the source code. Must you really have another piece of software standing in the middle?
Either you're a masochist or you've never worked on a large long-term project.
Quote:Original post by aCynic2Quote:Original post by Omid GhavamiQuote:Original post by aCynic2
Emacs + gcc == purity.
jed is also a nice editor that provides a link to gcc, color syntax highlighting, etc...
It's just that emacs can do EVERYTHING you need.
Where's your debugger?
gdb hooks into emacs quite nicely.
Well I guess that makes Emacs + gcc == purity with lacking functionality. The simple clean solution is nice and all but if you're working on serious projects functionality comes first and you'll eventually end up with more or less the same package.
Quote:Original post by Omid GhavamiQuote:Original post by Vuk Samotnjak
For most things I just use either Gedit or Vim to write source code, and I compile with the gcc from the command line. If I ever need some overly specific compile configuration, or I need to link to more than a few libraries, I just use a makefile.
Personally, I think most IDE's are far too over-bloated and just downright unnecessary for the most part. I mean you have your source code, and then you have the compiler -> compile the source code. Must you really have another piece of software standing in the middle?
Either you're a masochist or you've never worked on a large long-term project.
Hey, I've been a professional software developer since the early 1980s. I've worked on many large long-term projects and am doing so as we speak. I use gvim, the command line, and the autotools exclusively for all development tasks except GUI design.
I am not a masochist.
I am very familair with my tools and techniques and I fail to see how some fancy GUI that takes up all my valuable screen real estate and make me move my hands over to the mouse can accelerate my development process.
I am not trying to proselytize here. I'm merely pointing out that it requires neither naivte nor ignorance to use tried-and-true traditional tools by preference.
I would, however, like to point out that several of the younger guys here at work have dropped their IDEs in favour of learning vi in an effort to improve their productivity -- and none of them have gone back.
--smw
Vi is awsome, but when tackling a large unfamiliar codebase, features like visual studios "Find all references" is like magic candy from the gods.
When working on a very consistently structured project, or something you have written mostly yourself heavyweight tools like MSVC just gets in the way IMHO.
When working on a very consistently structured project, or something you have written mostly yourself heavyweight tools like MSVC just gets in the way IMHO.
Quote:Original post by BregmaQuote:Original post by Omid GhavamiQuote:Original post by Vuk Samotnjak
For most things I just use either Gedit or Vim to write source code, and I compile with the gcc from the command line. If I ever need some overly specific compile configuration, or I need to link to more than a few libraries, I just use a makefile.
Personally, I think most IDE's are far too over-bloated and just downright unnecessary for the most part. I mean you have your source code, and then you have the compiler -> compile the source code. Must you really have another piece of software standing in the middle?
Either you're a masochist or you've never worked on a large long-term project.
Hey, I've been a professional software developer since the early 1980s. I've worked on many large long-term projects and am doing so as we speak. I use gvim, the command line, and the autotools exclusively for all development tasks except GUI design.
I am not a masochist.
I am very familair with my tools and techniques and I fail to see how some fancy GUI that takes up all my valuable screen real estate and make me move my hands over to the mouse can accelerate my development process.
I am not trying to proselytize here. I'm merely pointing out that it requires neither naivte nor ignorance to use tried-and-true traditional tools by preference.
I would, however, like to point out that several of the younger guys here at work have dropped their IDEs in favour of learning vi in an effort to improve their productivity -- and none of them have gone back.
--smw
Are you developing with a command line debugger?
I find vi/emacs much better in editing source code files than VS but VS has a very nice and powerful debugger that I think is a terrific productivity booster.
Quote:Original post by rollo
Vi is awsome, but when tackling a large unfamiliar codebase, features like visual studios "Find all references" is like magic candy from the gods.
Wow, Visual Studio can perform a recursive grep at the push of a button, just like gvim? That is hawesome.
--smw
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
