Re: Typecache does not contain include tags created at expansion

Steven Rémot <[email protected]> Thu, 12 Feb 2015 08:11:20 +0100
Newsgroups gmane.emacs.cedet
Message-ID <[email protected]>
Le 30/01/2015 03:03, Eric Ludlam a écrit :
> On 01/24/2015 06:35 AM, Steven Rémot wrote:
>> OK, I think I got it : I did not override `semantic-find-tags-included'
>> for php-mode, and this was required to find include tags defined inside
>> a namespace. When "semantic/bovine/c" is loaded, it overrides
>> `semantic-find-tags-included' for c-mode. As php-mode derives from
>> c-mode this solves the issue.
>
> I'm glad you found the solution.  I wouldn't have guessed that php 
> inherited from C.  There are probably several other overrides that php 
> shouldn't be inheriting from C.
I already got some C overrides that messed up with wisent-php code, but 
this is the first one that instead fixes something!

>
>> Now, I wonder what is the cleanest way to solve the issue: I can define
>> `semantic-find-tags-included' in php-mode, and that will avoid a
>> dependency to "semantic/bovine/c". However, the code will be exactly the
>> same, so this leads to duplication. On the other hand, I can still load
>> "semantic/bovine/c" to share code and avoid duplication, but this leads
>> to one more dependency.
>
> It is probably better to duplicate, because php is bound to require a 
> few more tweaks that are different from C as you improve support.  I 
> don't know enough about php to guess what though.

I realise I will probably tweak a bit this function (actually I already 
rewrote it to create include tags dynamically instead of letting them in 
the buffer's tag list, where they actually have no dedicated region), so 
I will duplicate it anyway. Thanks for the advice.

>
>> 2015-01-21 23:01 GMT+01:00 Steven Rémot <[email protected]
>>
>>         I can't find anything about the "using" tag in the manual. I
>>         already saw it in the code for C++ support, is this tag specific
>>         to this language ?
>
> It is specific to C++, but happens to be known in the core scope 
> handling code.  As such, it should probably get propagated up to be 
> with the other top tags like function, etc.

If this is implemented in the core code I will take a look at it. This 
may help me on my current issue. Thank you for pointing it.

------------------------------------------------------------------------------
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/
_______________________________________________
Cedet-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cedet-devel