Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign

Please let CC to support the global namepace

<< < (2/4) > >>

MortenMacFly:

--- Quote from: blueshake on January 17, 2010, 08:02:23 am ---Patch for it. :D
[...]
welcome to test it.

--- End quote ---
Nice one. Can you do me a favor (for the future) and comment such changes? It's not very clear in the first place what the if statement actually means. Thanks! :-)

MortenMacFly:

--- Quote from: Loaden on January 06, 2010, 10:39:41 am ---I try to add a rule, and adding this rules, and CB not start now.

--- Code: --- <::>
<![CDATA[]]>
</::>
--- End code ---

--- End quote ---
You do know how often "::" appears in C++ code (e.g. MyClass::MyMethod)?! ;-)

blueshake:
well.

it mean nothing if the tokenType  is not pttSearchText.

for example:

for global codecompletion,such codes:

::abc

when we type these codes,the search will break the texts(::abc) into two compesents.

one is "" ,type is pttNameSpace
another is "abc" ,type is pttSearchText.

blueshake:
continue my comment.

so for pttNameSpace type ,if its text(tok) is empty.we need to eat this component.that is why the statement  tok.Length() != 0 in the if condition.
but for pttSearchText type ,we can not do this.because for such search codes(ss:: ),so we need another statement tokenType == pttSearchText in the if condition too.

ollydbg:

--- Quote from: blueshake on January 18, 2010, 02:48:08 am ---continue my comment.

so for pttNameSpace type ,if its text(tok) is empty.we need to eat this component.that is why the statement  tok.Length() != 0 in the if condition.
but for pttSearchText type ,we can do this.because for such search codes(ss::),so we need another statement tokenType == pttSearchText in the if condition too.

--- End quote ---
So, you mean: if we breakUP this statement"::abc".
We should result only One ParserComponent. right?

Navigation

[0] Message Index

[#] Next page

[*] Previous page