Re: semantic-format-tag-summarize does not return correct tag appearance

Eric Ludlam <[email protected]>
Newsgroups gmane.emacs.cedet
Message-ID <[email protected]>
On 12/02/2014 10:18 PM, Tu Do wrote:
> For example, if I have this single line in a C file:
> *
> const char** filename;*
>
> Running (semantic-fetch-tag) returns this list:
>
> (("filename" variable (:pointer 1 :constant-flag t :type "char") nil
> #<overlay from 1 to 22 in 03-095759.c>))
>
> It indicates the char pointer has 2 level of pointers. However, when
> running (semantic-format-tag-summarize), this is the result string returned:
>
> *Variables: const char filename*
>
> There's no pointer marking in char. This affect commands that use this
> function, like helm-semantic-or-imenu
> <http://tuhdo.github.io/static/part3/helm-semantic-or-imenu.gif>.

Hi Tu,

Using the version of CEDET in git, which I'm pretty sure is the same as 
current bzr, I tried a .cpp file with this in it:

const char ** filename;

as you did, and it produced:

(("filename" variable
   (:pointer 2 :constant-flag t :type "char")
   (:filename "/tmp/foo.cpp")
   #<overlay from 3 to 26 in foo.cpp>))

and when I used semantic-describe tag, it said:

Variables: const char** filename


This runs through some custom code in the semantic/bovine/c.el are for 
formatting tag types for c-mode (from which c++ mode inherits) to get 
the ** in there.

If you are using some other language, perhaps or mode setup, perhaps 
there is something broken connecting the overrides together?

Eric

------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.