This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Code assistance with GCC

On Wed, Apr 21, 2010 at 06:23:44PM -0700, Chris Lattner wrote:
> On Apr 21, 2010, at 1:51 PM, Manuel López-Ibáñez wrote:
> >>>>
> >>> 
> >>> This approach seems highly, uh, "inspired" from the exact same
> >>> functionality in Clang.  Any reason not to contribute to that
> >>> effort?
> >> 
> >> Surely trying to persuade people to contribute to some other project
> >> rather than gcc is off-topic here.  Even if not, it's pretty hostile.
> > 
> > Would such a feature be accepted in GCC? Otherwise, this seems like a
> > misunderstanding. Chris was not suggesting to contribute to Clang
> > instead of GCC but instead to contribute to the Clang completion
> > library rather than create your own 1-person project. Or at least this
> > is how I understood it.
> I actually meant to respond to him personally, I apologize for cc'ing the list.
> I did this because the other responses made it seem that it wasn't
> something that would be accepted back into GCC proper.  Maintaining an

Can you point at any response that said it would not be accepted back into
GCC proper?  There were no such comments AFAIK.  All that has been said
is that it is not possible to implement it AS A PLUGIN, at least not currently
and would probably require way too many hook points unless it wants to do
only code completion after . and -> (and not e.g. after :: and many other
tokens).  For C++ tentative parsing is probably the biggest problem that
needs solving.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]