![]() ![]() those working on Linux, are perhaps better off regressing back to the command-line environment of the 1980s than using any of these GUI tools-that way, at least one has no expectations to begin with.ĭear Soud, and also other readers using C++ and Eclipse:Ġ. ![]() ![]() So, all in all, the C++ programmers, esp. (I have not seen the Intel compiler in the recent years though.) (ii) Ever since the infinitely wise people in Redmond, WA, USA, decided to change the VC++ IDE from what it used to be until VC6 and to what has now become of it, no great GUI tool is at all left, on any platform-Linux or Windows. (i) Eclipse might be great for LaTeX "programming," and it perhaps may be good enough also for FORTRAN (simply because a superior alternative has never existed for Fortran the way VC6 was for C++), but it clearly is not good enough for C++ programming. And, with its ambitions for a more general use now curtailed, it is more or less only of historical interest for a C++ programmer working on the desktop and the higher-performance platforms. However, they also imposed a highly straight-jacketed user experience-the IDE didn't have even a quarter of the customizability of VC6 and even 10% of ease of use while debugging. For a few years in the mid and late naughties, QT environment was highly stable. It has crashed at the frequency of about twice a day, even for the same normal serial programming. within the last couple of months) it has proved me wrong. In contrast, I thought, Code::Blocks would be more stable because it's written in C++. If a Java implementation has bugs (or if the already fixed ones creep back in the next release), then it directly affects how Eclipse behaves at run-time. I guess that the biggest run-time weakness of Eclipse is that it is Java-based. The most important reason is that they chased the non-C/C++ languages, even VB, and tried to drag C++ down to their level.) (The VC after 6 has remained fairly stable, but it has lost almost all of its coziness. In the meanwhile, Code::Blocks seemed to have a more clunky-looking GUI interface, but its design seemed to be more suited to a C++ programmer migrating from the extremely stable and the absolutely cozy world of the VC++ 6, to these open-source tools. And, in view of its flakiness, the design philosophy seems to be much better than its implementation. With Eclipse, the design philosophy seems to be of too general in nature to be of direct relevance for the distinctive needs of a C++ programmer. Earlier, I had used Eclipse in my professional work also back in 2005, and my experience even back then was not worth writing anything home about. This experience with Eclipse was about a year ago or two. I was doing just an ordinary serial C++ program. A couple of times, it simply froze I had to manually kill the entire process (I mean the Eclipse itself.) And, I was not doing some "heavy-duty" work (like even the shared-memory multicore programming, let alone the cluster programming). But flakiness of the kind Eclipse still exhibits-failing to kill a previous debugger instance-is absolutely intolerable. You could spend some time initially, have your customization in place, and once done with that, then proceed smoothly later on. Here, I don't care if you have to customize Eclipse a lot before you can use it very effectively, and if this customization process itself is not well documented in an easily accessible form. And, it didn't have great usage-metaphors for the specific debugging needs of a C++ programmer. How flaky? Sometimes it failed to kill a previous debugger instance. Though it has a GUI that looks great to the first-time user, the last time I tried to use it, it (still) was a bit flaky. ![]() I have tried to use Eclipse, but mostly for C++ programming. If you need any help in terms of setting up, please let me know. And the debugger is very powerful though it is a small (in size) tool. It may solve some of the problems that we face in terms of compatible version of compilers, copyright issue. I am currently using Eclipse JUNO (4.2) and doing Fortran, C and C++ coding successfully. You need to do some setup which has been described here very nicely. It is maintained properly and has very good support team.Ībove link is basically for the fortran.Need only Java SDK with the fortran compiler if you want to do Fortran coding.Does not require installing, so some sort of portable.Very light weight (Zip size=~197MB, Real size=~450MB).Many reserachers are facing problem with versions, appropriate compiler or even with copyright issue. We usually use Microsoft visual studio's version to do Fortran/C/C++ coding. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |