Visual D 0.49.0-beta1

[Rainer Schuetze]

Thanks for the feedback.

On 17/03/2019 01:07, Michelle Long wrote:
[...]
> 
> Best I can tell is visual D is building phobos every time... This
> happens even if I made a change to a single file and recompile. It used
> to not do this.

Hmm, it doesn't do it here. You can get some info why it happens if you
enable global options "show why a target is rebuilt".

> 
> I see no reason why it would have to rebuild phobos every time since
> nothing changes. Disabling private build removes the errors. Maybe an
> option to use build only if it does not exist so it does not rebuild
> every time.

There is no real dependency check for the private phobos build, only
whether the file exists and whether the command line options or the
environment have changed.

> Also, does building multiple object files reduce compilation by not
> rebuilding everything? Seems like a lot of files are recompiled that
> don't change at all.

The single file compilation only happens for the C files in phobos,
everything else is built with a single invocation. see
privatephobos.lib.build.cmd in the output folder.

> 
> 
> 
> ...and at the page
> http://rainers.github.io/visuald/visuald/StartPage.html, would it be
> possible to have a search that restricts to that info?

The navigation bar is borrowed from the main D site, I'll have a look
whether the search can be modified to be restricted to the Visual D
pages ("Entire Site" is also misleading as it points to dlang.org instead).

> 
> 
> 
> There also seems to be an error in that a command line option -gc is
> being used by Visual D for "generate debug info suitable for mixed
> debugger" in the debug options. Disabling that options removes the switch.
> 
> 
> -gc seems to go with Visual studio while -g is for mago.
> 
> Not sure what they are suppose to do but dmd does not accept -gc.

-gc has been recently removed from the dmd command line. I think that
recent versions of the VS debugger (without mago) no longer need the
patches implied by -gc, but I'll have to verify.

> 
> You might want to add an option for -gf Emit debug info for all
> referenced types  to the debug properties.

This is option "Generate full debug information".

> 
> Another thing: When I do a search for a variable and the Visual D search
> window pops up for multiple matches, double clicking any entry does not
> take me to the file and location of that entry making me manually find
> the entry.
> 

The symbol search works by analyzing JSON-files generated by the
compiler. These can be outdated (for phobos you have to run "Build
phobos browse info" once after changing the compiler - it's been
proposed to do this automatically, see
https://issues.dlang.org/show_bug.cgi?id=18841, but that needs some
update check).

For your own code, the JSON generation must be enabled in the project
options. It reflects the state of the last successful build, though, not
any later edits.