<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>Re: C++ Compiler Suggestions! </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>ALErs -<BR>
<BR>
On Mon, 13 Jul 2009, Marc Ferguson wrote:<BR>
><BR>
> Thanks Richard,<BR>
> Really, VIM or EMACS? Nothing close to Borland or Visual Studio!? :)<BR>
<BR>
Depends on what was important to you in the Win IDE you were using. I found Visual Studio and Borland's [Pascal] products great ways to learn a language because they link to a lot of specifications and code examples. I haven't found anything like this is Linux, but these aren't what I want from and IDE any more: I'm more interested in getting smoothly around the code to either understand it or fix it.<BR>
<BR>
I generally use Source-Navigator for code analysis (just like it's name) and 'emacs' for most debugging. (You can even use 'emacs' as your editor in S-N and have the best(?) of both worlds. I also find S-N's 'project editor' both easier and stronger than VS. I appreciate using 'gdb' through both 'Insight' and 'emacs' as primary debugger, but I don't like "raw" 'gdb' very much. (There are scads of wrappers out there for 'gdb'. I wonder why? &8*)<BR>
<BR>
The *NIX tools don't give you much help as a beginner but you can expect more flexibility as you become an experienced user.<BR>
<BR>
Basically a religious argument. Spend some time with a tool and you mold your style to its strengths and steer away from its awkward corners.<BR>
<BR>
Ask lots of questions on ALE (but _never_ "What's the best widget to do ***?") and you can expect ultra competent help.<BR>
<BR>
Enjoy.<BR>
<BR>
- Mills<BR>
</FONT>
</P>
</BODY>
</HTML>