[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Code completion does not propose class members declared below cursor (bug 103857)
|
That's funny. I only remember the tEOC. I thought it was a clever way to stop the parser at the cursor.
But I do notice that code using tCOMPLETION that isn't mine. "fHandledCompletion= true;" isn't something I'd write. I hate prefixes on methods and functions (f), and I always put spaces around the operator. But I'm sure you could prove me wrong again ;).
Both seem to be used, though, so be careful.
On Sun, Oct 11, 2009 at 9:49 PM, Sergey Prigogin
<eclipse.sprigogin@xxxxxxxxx> wrote:
Hmm... According to CVS history, tCOMPLETION was introduced by dschaefer on 2/18/05 and tEOC was introduced by the same person three days later.
-sergeyOn Sun, Oct 11, 2009 at 5:36 PM, Doug Schaefer
<cdtdoug@xxxxxxxxx> wrote:
Not sure, when I was working on it tEOC was the only one. Essentially it was a special case of tEOF since we only parsed up to the cursor location.
Not sure what tCOMPLETION is. Maybe someone's been in there to help fix some of the deficiencies the short parse introduces.
Doug.
I'd like to start working on
bug 103857. As a preliminary step I'm collecting information about current design of code completion. In particular, I'm interested in tCOMPLETION and tEOC tokens. Why there are two separate tokens? What role each of them plays? Do these two tokens always share the same location? A detailed answer from somebody familiar with the current design will be highly appreciated.
Thanks,
-sergey
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
