Date: Mon, 09 Jan 2006 10:25:24 -0500 From: JD Arnold <jdarnold@buddydog.org> To: freebsd-questions@freebsd.org Subject: Re: Which is the best open source C/C++ IDE out there? Message-ID: <dptv94$7ft$1@sea.gmane.org> In-Reply-To: <20060109140254.92455.qmail@web33306.mail.mud.yahoo.com> References: <666bdb140601081330m3b394a02v@mail.gmail.com> <20060109140254.92455.qmail@web33306.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Danial Thom wrote:
>
> --- Vladimir Tsvetkov <npacemo@gmail.com> wrote:
>
>>> This is obviously a trick question, because
>> real
>>> programmers don't use IDEs. Case Closed.
>> I'm not a real programmer, but UNIX is a great
>> developer environment.
>> It's a tool based environment.
>> Small tools, strong cohesion in what they are
>> designed for, easy ways
>> to combine them to form more complex tasks.
>> Good documentation too.
>> Actually you don't need anything else, you
>> don't need a colourfull IDE. But...
>> Maybe only few, really exceptional people can
>> benefit and grok the
>> power of this kind of environments.
>> To me the ideal "IDE" is actually a toolkit:
>> - Source Editor, preferably with a object
>> browser or other kind of a
>> source browser. An autocomplete functionallity
>> could increase
>> productivity too - this could increase quality
>> if we measure quality
>> of code by the low number of syntax mistakes,
>> but this could also be a
>> threat to quality letting the programmer write
>> without reading
>> carefully what is written - code bloating.
>> - Compiler with a debugger. We must discuss
>> about the pros. and cons.
>> of a grafic debugger versus a text-mode
>> debugger. The things are
>> getting really messy when it comes up to
>> debugging multithreading code
>> and I really don't know what is the ultimate
>> tool for this task.
>> - A build tool. Ant or make will suffice.
>> - Source control tools. CVS, SVN etc.
>> - Documentation tools. POD, Doxygen, Javadoc or
>> something else.
>> - Unit testing framework. This is not always a
>> tool. This could be a
>> language extension, or a testing API.
>> - Other tools.
>>
>> You don't need to put everything together in a
>> single swissknife-tool,
>> but this could be convenient in some cases.
>>
>> IDE vs. Toolbased Environments ???
>>
>> Which is more productive and how to measure
>> productiveness?
>>
>> Best Regards,
>> Vladimir Tsvetkov
>
> Tools, schmools. vi and cc work for me.
>
> I do admit that I wish someone would get make to
> accept spaces instead of the (damn) tab. I think
> its time for that :)
That's why you should graduate to Emacs - with the makefile syntax highlighting,
you'll at least see the differences between tabs and spaces before getting into
trouble due to bad whitespacing!-)
--
Jonathan Arnold (mailto:jdarnold@buddydog.org)
Daemon Dancing in the Dark, a FreeBSD weblog:
http://freebsd.amazingdev.com/blog/
UNIX is user-friendly. It's just a bit picky about who its friends are.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dptv94$7ft$1>