From: Benjamin Rutt <rutt.4@osu.edu>
Subject: Re: Extensions to make C/C++ development easier?
Date: Mon, 11 Sep 2006 23:48:36 GMT [thread overview]
Message-ID: <87d5a26ka6.fsf@penguin.brutt.org> (raw)
In-Reply-To: 87fyez7nrt.fsf@kip.sateh.com
Stefan Arentz <stefan.arentz@gmail.com> writes:
> Thorsten Bonow <thorsten.bonow@post.rwth-aachen.de> writes:
>
>> >>>>> "Stefan" == Stefan Arentz <stefan.arentz@gmail.com> writes:
>>
>> Stefan> What are the favorite extensions here for making C/C++ development
>> Stefan> easier?
>>
>> Stefan> I'm used to a Java IDE with symbol completion, lookup of
>> Stefan> documentation, completion on structs/classes, etc. Are those things
>> Stefan> available for emacs when doing C/C++ development?
>>
>> Stefan> S.
>>
>> Hi,
>>
>> this is a FAQ.
>>
>> You should google for related threads or things like "semantic/cedet,
>> intellisense, cscope or gtags". A good starting point is the programming section
>> of the emacs wiki.
>
> I've looked at the wiki and I see many possibilities. I am however more
> interested in some opinions and real world experience. What works, what
> doesn't work.
In my experience just etags and dabbrev really work among your list
above. I never had any real luck with semantic for C++. I use my
package msf-abbrev to make C++ as well as other development easier for
anything repetitious.
--
Benjamin Rutt
next prev parent reply other threads:[~2006-09-11 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 10:01 Extensions to make C/C++ development easier? Stefan Arentz
2006-09-10 10:43 ` Thorsten Bonow
2006-09-10 15:19 ` Stefan Arentz
2006-09-11 23:48 ` Benjamin Rutt [this message]
2006-09-12 15:28 ` robert.thorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d5a26ka6.fsf@penguin.brutt.org \
--to=rutt.4@osu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).