User forums > Nightly builds

The 16 august 2006 build is out.

<< < (9/9)

phlox81:

--- Quote from: MortenMacFly on August 18, 2006, 09:16:54 am ---
--- Quote from: phlox81 on August 18, 2006, 09:04:34 am ---[...] that when typing str it gets "completed" to strcasecmp, [...]

--- End quote ---
Are you aware that you can setup when CC actually pops up (Settings->Editor->CC)? I've set this option to 5 letters thus it doesn't pop up too often (for 1-4 letters words it usually makes no sense at all). I still can trigger it manually, of course using the hotkey. Maybe this will help you, too.

--- End quote ---

Well, thats a workaround, but no solution ;)
I've set that to 3 letters, because the old one was mostly guessing right, or
not finding anything. With 5 letter I would not have the problem so often,
but as I said, for me, a workaround is not a solution.
Once the local scope gets recognized, the problem might solve itself. (hopefully)

mandrav:

--- Quote from: phlox81 on August 18, 2006, 09:04:34 am ---But maybe, it should be more intelligent, I parsed now every thing, and it knows now a lot of stuff, most
of what it shows it totally useless.

--- End quote ---

"Great work" and "totally useless" don't go together in the same paragraph. Please decide :lol: .


--- Quote from: phlox81 on August 18, 2006, 09:04:34 am ---Especially with local variables it gets annonying, that when typing
str it gets "completed" to strcasecmp, maybe you could fix that it autoselects the first value by default.
But if you're working on the local scope, than it might already fixes this...

--- End quote ---

If "str" is not recognized (i.e. local scope not parsed correctly), don't expect it to appear in the list.
Just a few minutes ago, I commited a couple of fixes for local scope:


- Fixed current function arguments parsing in code-completion. Didn't work all the time.
- Remove all temporary code-completion tokens (like local variables) before starting a new search.


All that's left now is improve the actual local block parsing and then I can move to more interesting and important stuff ;).
Before you ask, these are:


* Recognize the "using namespace" construct.
* Parse typedefs.
Quite big tasks, both, but interesting :).

phlox81:

--- Quote from: mandrav on August 18, 2006, 10:36:11 am ---
--- Quote from: phlox81 on August 18, 2006, 09:04:34 am ---But maybe, it should be more intelligent, I parsed now every thing, and it knows now a lot of stuff, most
of what it shows it totally useless.

--- End quote ---

"Great work" and "totally useless" don't go together in the same paragraph. Please decide :lol: .

--- End quote ---

Sometimes your great Work shows partly useless information. ;)
For example, I'm using boost::spirit in my project, when typing anything, I get to see
the internals of boost::spirit. Or when typing str I get to see things, where I don't
even know from where they are, and what the could be (STL? wxWidgets? boost?).
On the other hand, seeing this information is also an improvement. Maybe the could
be a switch, for showing only global types, and only parse the locally used types
for more information.
But as you said, local vars aren't parsed for now, so it can't show any of them, so I will wait ;)
But when typing a membervar, I get to see the correct information, which is great :)

As a programmer I know, how much effort and work such a thing is, so I am impressed
by the good job you did there. I work on a tool for codegeneration, and not have done
so much parsing, but some for functions with boost::spirit, but I still gotta improve that :)

phlox

Navigation

[0] Message Index

[*] Previous page