From: Chong Yidong <cyd@stupidchicken.com>
To: "Eric M. Ludlam" <eric@siege-engine.com>
Cc: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>,
cedet-devel@lists.sourceforge.net,
Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: [CEDET-devel] ede-linux doesn't work with master emacs repo
Date: Tue, 28 Sep 2010 19:48:09 -0400 [thread overview]
Message-ID: <87ocbhpgzq.fsf@stupidchicken.com> (raw)
In-Reply-To: <4CA262FA.7080906@siege-engine.com> (Eric M. Ludlam's message of "Tue, 28 Sep 2010 17:49:46 -0400")
"Eric M. Ludlam" <eric@siege-engine.com> writes:
> First, your C file (with Aneesh's example) needs to be parsed correctly.
>
> M-x bovinate RET
>
> will dump out the results.
Here's what I get:
(("a" type
(:members
(("k" variable
(:type "int")
(reparse-symbol classsubparts)
#<overlay from 16 to 22 in foo.c>)
("b" variable
(:type "char")
(reparse-symbol classsubparts)
#<overlay from 27 to 34 in foo.c>))
:type "struct")
nil #<overlay from 1 to 39 in foo.c>)
("t" variable
(:type
("a" type
(:prototype t :type "struct")
nil nil))
nil #<overlay from 1 to 39 in foo.c>)
("main" function
(:type "int")
nil #<overlay from 41 to 113 in foo.c>))
I notice that the unlink-copy-hook entries are not present. The above
results are identical to the bovinate output for Emacs 23.2 with
built-in CEDET.
next prev parent reply other threads:[~2010-09-28 23:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 4:03 ede-linux doesn't work with master emacs repo Aneesh Kumar K.V
2010-09-25 19:19 ` Chong Yidong
2010-09-25 21:03 ` Aneesh Kumar K. V
2010-09-25 22:37 ` Eric M. Ludlam
2010-09-25 23:28 ` [CEDET-devel] " Chong Yidong
2010-09-26 2:58 ` Eric M. Ludlam
2010-09-28 14:49 ` [CEDET-devel] " Aneesh Kumar K. V
2010-09-28 16:33 ` Chong Yidong
2010-09-28 21:49 ` Eric M. Ludlam
2010-09-28 23:48 ` Chong Yidong [this message]
2010-09-29 2:39 ` Eric M. Ludlam
2010-09-29 7:43 ` David Engster
2010-09-29 16:05 ` Chong Yidong
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=87ocbhpgzq.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cedet-devel@lists.sourceforge.net \
--cc=emacs-devel@gnu.org \
--cc=eric@siege-engine.com \
/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.