Re: c/c++ project management and debugging

[Elena]

On Dec 21, 5:42 pm, Rajinder Yadav <devguy...@gmail.com> wrote:
> On Tue, Dec 21, 2010 at 9:52 AM, Richard Riley <rile...@googlemail.com> wrote:
> > Rajinder Yadav <devguy...@gmail.com> writes:
>
> >> On Tue, Dec 21, 2010 at 8:10 AM, Elena <egarr...@gmail.com> wrote:
> >>> On Dec 21, 12:00 pm, Rajinder Yadav <devguy...@gmail.com> wrote:
> >>>> i've never had the need to create a makefile or edit one by hand when i
> >>>> code using visualstudio, all i care about is coding my project in C++
> >>>> and getting on with life.
>
> >>> You don't know what a professional IDE is then, and why Emacs isn't up
> >>> to the task.
>
> >> yes i do, you missed my point
>
> >>> If you are doing professional C++ development, then you are tweaking
> >>> your project settings all the time.  The VC++ Project Settings dialog
> >>> is just a wrapper on top of a "Makefile" kind-of generator.  What VC++
> >>> does that Emacs doesn't is setting default values which work unless
> >>> you have special requirements.  That's why you felt that all you had
> >>> to care about was coding your project in C++.  Development in Emacs
> >>> does not give such luxury.
>
> >>>> i love ruby on rails hacking, i love doing everything from the command
> >>>> line, it's more faster and efficient coding a rails app when compared to
> >>>> doing it with netbeans + ide, or whatever IDE is out there!
>
> >>> Obviously, for hobbyists, an IDE is overkill.
>
> >> you're saying ruby on rails is for hobbyists? btw, ide is not an
> >> overkill, it's just you don't need an ide because rails comes with
> >> tools like rake and generators that frankly is faster doing thing at
> >> the command line with a simple text editor and terminal, reason i
> >> choose emacs to code ruby on rails stuff, i started off with IDE like
> >> netbeans but it just didn't feel right (for me, for others it's the
> >> right choice)
>
> > Then the IDEs you have used have not been configured IDEs. Its almost
> > never quicker anymore at the command line in a properly configured
> > IDE. A lot of people claim it is : invariably those who have not used a
> > modern IDE. Those things you do at the command line can be hot keyed in
> > an IDE too. As for "not needing" - do you know what an IDE is? I
> > actually use emacs as one - weaknesses not withstanding - so I kind of
> > disagree with Elena about that. Development is a lot more than "coding
> > in a text editor". Lets see what the IDE brings (and most of what Emacs
> > can do already and marked appropriately in brackets below):-
>
> in the case of rails coding, you can easily get by with the command line
>
> i can type,
>
> rails g model post name:string ...

This could be done in an IDE by means of an interactive macro, very
easy to code, without having to click anything.

>
> faster than I can click on a menu, open a dialog, then click on each
> field and type in stuff, click on the ok(generate) button to generate
> a model + boiler-code.

If an IDE does not allow to automate recurring tasks, or forces you to
use menus, it isn't a decent IDE: dump it.

>
> pretty much most of the rails development in done this way. it follows
> conventions over configuration (you're not editing makefiles, etc),
> suffice to say you don't need an IDE for rails coding and anyone will
> be faster with the command + basic editor than with a IDE setup for
> rails.

Because they lack a decent IDE, Rails coders have to resort to a basic
editor + command line.  That is not to say that IDEs aren't better.
They are not available, that's a different story.