[Extrawurst]

I am seeing all those exciting stuff you check in lately, syntax parsing for errors and such. when is a new release planned ?

[sagitario]

Not too long, but I'm not yet sure about the negative impact of the parsing on editing speed, so I'm trying it out for some time myself. If you want to give it a test drive, I've uploaded an rc1 to the download folder.

Using std.datetime as a test case, both parsing and outlining cause a bad slow down for me. You can disable them on the Text-Editor->D->Colorizer option page, but you need to reopen the file for the changes to take effect.

[Extrawurst]

up to now i did not find any performance problems, yet. but i must say i do not use very long module in my own modules...

BUT, the errors should be red underlined or something, because now you have to accidentally move the cursor where the error was found

example:
module main;

import std.stdio;

int main(string[] argv)
{
writeln("Hello D-World!")
return 0;
}

if you move over return a tooltip saying "line 9 'return': ';' expected" pops up. First this is quite difficult to understand, better would be something like "found 'foo': expected 'bar'" and of course a red line showing me that the parser found an error in the first place

[sagitario]

The underlining works for me (VS2008). I will check VS2010 soon.

The error messages surely need improvement, but the parser reports only very simple errors. The really interesting ones are in the semantic phase, and that is still some way to go...

[sagitario]

I've finally found some time to investigate the missing underlining. I was using some undocumented line coloring feature to do it, but that does not work in VS2010 anymore. It is now implemented the official way. Please try rc2 from the download folder.

[Extrawurst]

Ok the underlining works now, nice!
What would be great now is when hovering an underlined text that the error is tooltipped then.

[sagitario]

[Zone]

I am playing with the new rc2 build and have found its pretty easy to crash it when doing the alt-drag to column select code, especially when the drag destination is off the screen (which is supposed to cause the code window to start scrolling).

I am using VS2010sp1


Also:
I'm sure you have a million things to eventually get to, but i've found that right click 'go to definition' works quite well in my own code. However there is an exception: modules only accessible through the path (like std.conv) but are not in the project can't be found by the 'go to definition' feature.

[sagitario]

[Zone]

Much more stable for me I abuse the column mode in 2010 quite heavily as its pretty nice (and more flexible than in previous versions).

I swear I built the browse info once but it might have crashed that session so didn't notice it doing anything different afterwards. Its definitely working now when i right click on an 'import std.conf' statement and it opens up the std.conv.d for me now . . . It definitely saves me time since I don't know what's all in the std.* files and need to look at them all the time


The only other crash I've seen seems to be harder to come up with a solid repro case. I'll definitely post something when I have something more definitive. My use cases are currently are refactoring C++ code and into D, while at the same time learning how to template and mixin the macros and other constructs. I believe this sometimes confuses the plugin to the point it hangs or crashes. Sometimes its a new file, other times its large blocks of commented out code I comment back in before its converted.

[Zone]

There is a good chance the plugin crashes on me when deleting a line

import myproject.myfile;

The use case is : I am refactoring my modules to be merged and removing the import statements from the dead or soon-to-be-dead files. There is a good chance the code in the file still relys on some of the symbols from the import and I haven't cleaned those up yet (I like letting the compiler tell me where they are so I can think about it . . .)

[sagitario]