From: Jai Dayal <dayalsoap@gmail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: A guide on setting up C/C++ development environment for Emacs
Date: Fri, 29 Aug 2014 09:16:20 -0400 [thread overview]
Message-ID: <CAMJ-YiTR-X7AvHjd+3Ebz-HwmiEVcJ5t0TQnA5Cb2qmX+Z9psA@mail.gmail.com> (raw)
In-Reply-To: <874mwv788b.fsf@wanadoo.es>
Actually, the topic of this thread is not CEDET's usability, but rather a
manual on how to setup various Emacs IDE tools.
Oscar isn't too bright and believes in Jesus. Someone of "faith" can never
be convinced; faith is idiocy by definition.
On Fri, Aug 29, 2014 at 9:09 AM, Óscar Fuentes <ofv@wanadoo.es> wrote:
> David Engster <deng@randomsample.de> writes:
>
> > Óscar Fuentes writes:
> >> However, I don't see CEDET's team throwing away their Elisp parser and
> >> start coding one on C/C++. They could use Clang's right away, or GCC's
> >> once the modularization is completed, but they insist on their own's.
> >
> > Stop this, Óscar. I think you're very well aware that the clang binary
> > in itself only provides smart completions, nothing more.
>
> I'm aware of the possibilities provided by libclang, which go *far*
> beyond than whatever the executable does.
>
> > I *have* added
> > support for this in CEDET. I'm pretty sure you know that as well,
> > because I've already written this to you the last time this was
> > discussed.
>
> Yes, there are a number of packages that interact with Clang. That is
> unrelated to the topic of this sub-thread: the usability of CEDET's
> built-in C++ parser.
>
> > What you are talking about is walking the AST using libclang/libtooling,
> > which is a whole different matter and nothing which one does "right
> > away". Just look at projects like rtags which do that, and see what it
> > entails.
>
> That's about 0.001% of the work required for implementing a C++
> parser/analyzer.
>
> > This is just to set things straight for others which are reading this. I
> > have absolutely no interest in further discussing this with you.
>
> Fair enough. And as I mentioned on that other discussion, this is not
> about you, David. Please don't take this personally.
>
> What irks me is that, whenever Emacs is compared to modern IDEs and
> features like smart code completion, refactoring, advanced code
> navigation and querying are discussed, CEDET is the Great Hand-waving
> Enabler. Since CEDET was regarded as the solution by the community,
> years passed, C++11 came, then C++14 and fact is that CEDET still can't
> handle C++ code that was ordinary circa 1995. The net effect is that
> Emacs is no longer competitive on the C++ realm and I cannot recommend
> it to my C++ colleagues and students. The only hope is that some third
> party package fixes this outside of the core Emacs development community
> (be it on top of CEDET or not).
>
> Of course, Emacs can also consider C++ a lost cause. After all, C++ has
> just a fraction of the user base of Java.
>
>
>
next prev parent reply other threads:[~2014-08-29 13:16 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 7:05 A guide on setting up C/C++ development environment for Emacs solidius4747
2014-08-27 12:48 ` Dmitriy Igrishin
2014-08-27 13:18 ` Tu Hoang Do
2014-08-27 14:15 ` Dmitriy Igrishin
[not found] ` <CAMd9FiKzwc1QKa3KtZPFpTGs86bupRptFqL_WwCSE3kPGARXfg@mail.gmail.com>
2014-08-27 14:53 ` Fwd: " Tu Hoang Do
[not found] ` <CAAfz9KNL25WboPXG87Azd_6yVr8zrx6hNrCsmuWs6w_XTvdspQ@mail.gmail.com>
[not found] ` <CAMd9FiJyjk78a-3yMatvca3qp+pr4O+GmDp03ZqFSkpAEoxhGw@mail.gmail.com>
2014-08-27 18:14 ` Tu Hoang Do
2014-08-27 18:15 ` Jai Dayal
2014-08-27 18:37 ` Óscar Fuentes
2014-08-27 18:42 ` Jai Dayal
2014-08-27 18:42 ` Jai Dayal
2014-08-27 18:52 ` Óscar Fuentes
2014-08-27 19:05 ` Jai Dayal
2014-08-27 19:28 ` Óscar Fuentes
2014-08-27 19:32 ` Jai Dayal
2014-08-27 20:06 ` Óscar Fuentes
2014-08-27 20:11 ` Jai Dayal
2014-08-27 20:57 ` Óscar Fuentes
2014-08-27 23:17 ` Jai Dayal
2014-08-27 23:47 ` Óscar Fuentes
[not found] ` <mailman.7678.1409181490.1147.help-gnu-emacs@gnu.org>
2014-08-28 3:30 ` Rusi
2014-08-28 3:33 ` Jai Dayal
2014-08-28 4:29 ` Óscar Fuentes
[not found] ` <mailman.7693.1409200204.1147.help-gnu-emacs@gnu.org>
2014-08-28 5:39 ` Rusi
2014-08-28 12:27 ` Jai Dayal
[not found] ` <mailman.7714.1409228889.1147.help-gnu-emacs@gnu.org>
2014-08-28 15:53 ` solidius4747
2014-08-28 21:22 ` Óscar Fuentes
2014-08-28 22:24 ` Stefan Monnier
2014-08-28 23:28 ` Dmitry
2014-08-29 0:02 ` Óscar Fuentes
[not found] ` <mailman.7793.1409270604.1147.help-gnu-emacs@gnu.org>
2014-08-29 3:35 ` Stefan Monnier
2014-08-29 6:06 ` David Engster
2014-08-29 13:09 ` Óscar Fuentes
2014-08-29 13:16 ` Jai Dayal [this message]
2014-08-29 13:45 ` Óscar Fuentes
2014-08-29 13:52 ` David Engster
2014-08-29 14:16 ` Óscar Fuentes
[not found] ` <mailman.7808.1409292429.1147.help-gnu-emacs@gnu.org>
2014-08-29 13:15 ` Rusi
2014-08-28 17:08 ` Rusi
2014-08-28 17:13 ` Jai Dayal
2014-08-28 19:43 ` Marcin Borkowski
2014-08-28 19:47 ` Jai Dayal
2014-08-28 20:15 ` Marcin Borkowski
[not found] ` <mailman.7743.1409246061.1147.help-gnu-emacs@gnu.org>
2014-08-28 17:26 ` Rusi
2014-08-28 23:01 ` Thorsten Jolitz
2014-08-27 18:45 ` Óscar Fuentes
2014-08-27 14:39 ` Thien-Thi Nguyen
[not found] ` <mailman.7608.1409150189.1147.help-gnu-emacs@gnu.org>
2014-08-27 15:01 ` solidius4747
2014-08-27 18:31 ` Óscar Fuentes
[not found] <mailman.127014.1409321829.1146.help-gnu-emacs@gnu.org>
2014-08-29 14:33 ` Tory S. Anderson
2014-08-29 17:21 ` Jai Dayal
2014-08-29 18:11 ` Marcin Borkowski
2014-08-29 18:15 ` Jai Dayal
2014-08-29 18:27 ` Marcin Borkowski
2014-08-29 18:34 ` Jai Dayal
2014-08-29 19:17 ` Marcin Borkowski
[not found] ` <mailman.7863.1409335908.1147.help-gnu-emacs@gnu.org>
2014-08-30 3:43 ` Rusi
2014-08-30 7:24 ` Thien-Thi Nguyen
2014-08-30 21:27 ` Jai Dayal
[not found] ` <mailman.7951.1409434065.1147.help-gnu-emacs@gnu.org>
2014-08-31 1:53 ` Rusi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMJ-YiTR-X7AvHjd+3Ebz-HwmiEVcJ5t0TQnA5Cb2qmX+Z9psA@mail.gmail.com \
--to=dayalsoap@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=ofv@wanadoo.es \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.