From: Dipanjan D. <its...@gm...> - 2012-08-21 06:04:00
|
On 21 August 2012 10:43, Nathan Ridge <zer...@ho...> wrote: > > >>> If you have to mess with makefiles in your IDEs, you're doing it wrong. > >>> Since you're already using MinGW with MSYS and messing with makefiles, > I > >>> suggest dropping the IDE, it gets in the way, use something sane like > vi > >>> or notepad++. > >> > >> An IDE serves multiple purposes: code navigation, auto-completion, > >> automated refactoring, building, interactive debugging, and others. They > >> are often better at some of those than others. It is perfectly > reasonable > >> to use an IDE for the things it's good at while doing other tasks > manually. > >> > >> In the case of Eclipse, I have found its code navigation and > >> auto-completion capabilities for C++ to be unmatched, because it fully > >> parses and semantically analyzes your code in the background and can > >> therefore do these tasks with very high accuracy. On the other hand, > I've > >> never liked its automatically generated makefiles, so I don't use that > >> feature, I write the makefiles manually. There is nothing inconsistent > or > >> "insane" about that. > > > > The IDE obscures vital information, hiding compiler and linker details, > > it is a crutch to new programmers, it is of no use to programmers just > > beginning to learn a language. Try looking for the preprocessor or link > > flag settings, it is buried deep somewhere in the preference page, > > you'll need to go play hide and seek with the IDE. > > It only hides those details if you use it to build your program. The use > I was describing is using the IDE for navigation and related features, > while writing the makefile yourself. > > > On parsing, I've tried Eclipse, Netbeans, CodeBlocks, DevShedC++, > > declaration parsing is buggy at best. Struct members go missing, auto > > complete stops working etc, especially if you use any compiler specific > > intrinsics or pragmas that the IDE may not know about, it may also have > > issues around ifdef preprocessor statements. It may also flag a valid > > piece of code as error. MS's Visual Studio is somewhat better in this > > regard, obviously, you'll need to code to MS's convention. > > > The latest version of Eclipse (Juno) works very well in my experience, > much better than previous versions. I can't comment on other IDEs. > > I am using Juno CDT for C code development. But the static code analyzer Codan works erratically. -- Thanks & Regards, Dipanjan |