Methods missing in Outline
Status: Beta
Brought to you by:
bernhardbrem
If the attached file is opened in the editor, the Outline view does not show all methods of class StyleCLI.
More precisely, "FormatProperty(...)" is the last method shown, and methods from "FormatEvent(...)" are missing. These are 7 methods total.
Likely, this bug is caused by the parser.
The file where this bug happens.
Logged In: YES
user_id=1299552
Originator: NO
Test case below will illustrate the problem:
class ErrorClass
{
void X()
{
StringBuilder sb = new StringBuilder ();
sb.Append("{");
sb.Append("set;");
sb.Append("};\n");
return sb.ToString ();
}
void V()
{
}
}
Logged In: YES
user_id=1299552
Originator: NO
Thanks for the report, Harald. This has been fixed in CVS HEAD. Please verify.
Logged In: YES
user_id=1736779
Originator: YES
Verified!
Logged In: YES
user_id=1736779
Originator: YES
I'm sorry, I have to re-open this bug.
The newly attached file "Expression.cs" cannot be scanned either. Same problem: Most of the source code is not parsed, starting at method DoParse(...).
File Added: Expression.cs
Logged In: YES
user_id=1736779
Originator: YES
Ad last comment: Actually, this was wrong and due to bug #1878266.
However, the parser skips several items.
Logged In: YES
user_id=1299552
Originator: NO
I've identified that the failure in Expression.cs is due to the fix that was implemented for the original problem. I have a proposed workaround but then the speed that it takes to parse a file seems to double in length. Will investigate further.
Logged In: YES
user_id=1299552
Originator: NO
Here are some trial runs I did before and after the fix, times are in milliseconds.
Before:
433
628
384
425
393
470
410
427
412
489
After:
958
1003
916
1008
929
1024
999
1126
Logged In: YES
user_id=1299552
Originator: NO
I've committed some changes to get the members showing but the hierarchical structure is currently off.
Logged In: YES
user_id=1299552
Originator: NO
Actually, this file is more complicated than I thought, there are still other things that aren't being parsed properly.
Logged In: YES
user_id=1299552
Originator: NO
Expression.cs should be fine now.