Re: [RFA] Compile objc-lang.c, objc-exp.tab.c [1/5]

[David Ayers <d.ayers@inode.at>]

Hello,

Please also keep in mind, that hopefully one day (now that the parser 
issue is being tackled in gcc) gcc will hopefully support ObjC++ code. 
(i.e. ObjC and C++ code in one file / member function / method.)  I'm 
not sure how this would play into the mechanics of language specific 
demangeling functions and how these mechanics would decided which 
function to use, but I just wanted to make sure everyone is aware of 
this when thinking about it.

Cheers,
David Ayers

Daniel Jacobowitz wrote:

>Not without some substantial thought.  We use cplus_demangle in a lot
>of places where we don't even know what the language is supposed to be
>- for minsyms, during lookups, et cetera.
>
>Certainly it needs to be thought about.  At least objc's mangling is
>probably not entirely ambiguous with C++/Java's?  I don't know.
>
>On Thu, Mar 20, 2003 at 04:27:02PM -0500, Andrew Cagney wrote:
>  
>
>>Daniel,
>>
>>Would it be possible to make the cplus_demangle() method part of the 
>>language vector?  That way code like the patch below could be reduced to:
>>
>>	/* Return demangled language symbol, or NULL.  */
>>	language_demangle (current_language, arg);
>>
>>This would in turn allow Adam to just add an equivalent objc_demangle() 
>>method to the objc language vector, and hence eliminate the need to 
>>always link in objc-lang.c.
>>
>>Andrew
>>
>>    
>>