Thread overview
VisualD temp D variables showing up
Dec 29, 2017
Amorphorious
Dec 29, 2017
Amorphorious
Dec 29, 2017
Amorphorious
Dec 30, 2017
Rainer Schuetze
Dec 30, 2017
Rainer Schuetze
Dec 30, 2017
Rainer Schuetze
December 29, 2017
I am computing equations involving ^^ and about 90%, around 40, temp variables are showing up in the locals window.

		__powtmp5173	.712227326	double
		__powtmp5174	.3275114687	double
		__powtmp5175	1	double
		dist	2.017358817	double
		__powtmp5176	-.2647196372	double
		__powtmp5177	1.225902886	double
		__powtmp5178	.6666666667	double
		__powtmp5179	5.563024167e-309	double
		__powtmp5180	3.613877664e-308	double
		__powtmp5181	1.424047271e-305	double
		__powtmp5182	0	double
		__powtmp5183	2.125183105	double
		__powtmp5184	3.124453764e-307	double
		__powtmp5185	2.769750648e+266	double
		__powtmp5186	1.700051445e-313	double
		__powtmp5187	2.826759824e-307	double
		__powtmp5188	1.447097644e-305	double
		__powtmp5189	1.295163447e-318	double
		__powtmp5190	1.447097644e-305	double
etc.

How can I remove these? I do not need to see them.

December 29, 2017
On Friday, 29 December 2017 at 11:25:09 UTC, Amorphorious wrote:
> I am computing equations involving ^^ and about 90%, around 40, temp variables are showing up in the locals window.
>
> 		__powtmp5173	.712227326	double
> 		__powtmp5174	.3275114687	double
> 		__powtmp5175	1	double
> 		dist	2.017358817	double
> 		__powtmp5176	-.2647196372	double
> 		__powtmp5177	1.225902886	double
> 		__powtmp5178	.6666666667	double
> 		__powtmp5179	5.563024167e-309	double
> 		__powtmp5180	3.613877664e-308	double
> 		__powtmp5181	1.424047271e-305	double
> 		__powtmp5182	0	double
> 		__powtmp5183	2.125183105	double
> 		__powtmp5184	3.124453764e-307	double
> 		__powtmp5185	2.769750648e+266	double
> 		__powtmp5186	1.700051445e-313	double
> 		__powtmp5187	2.826759824e-307	double
> 		__powtmp5188	1.447097644e-305	double
> 		__powtmp5189	1.295163447e-318	double
> 		__powtmp5190	1.447097644e-305	double
> etc.
>
> How can I remove these? I do not need to see them.

Also, tuple display is quite verbose, can it be removed too?


+		[0]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[1]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[2]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[3]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[4]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[5]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[6]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[7]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[8]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[9]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[10]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[11]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[12]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[13]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[14]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[15]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[16]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[17]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[18]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[19]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[20]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[21]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[22]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[23]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[24]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[25]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[26]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple
+		[27]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[28]	{__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}	std.typecons.Tuple!(double, double, double).Tuple
+		[29]	{__expand_field_0=-.4901682775, __expand_field_1=-.05324527881, __expand_field_2=.87}	std.typecons.Tuple!(double, double, double).Tuple

December 29, 2017
Also, when I put a BP on an if statement it is not hit and Visual D says that no symbols have been loaded for the document. If I put the BP on a line that isn't an if statement, it hits the BP fine.

December 30, 2017

On 29.12.2017 12:25, Amorphorious wrote:
> I am computing equations involving ^^ and about 90%, around 40, temp variables are showing up in the locals window.
> 
>          __powtmp5173    .712227326    double
>          __powtmp5174    .3275114687    double
>          __powtmp5175    1    double
>          dist    2.017358817    double
>          __powtmp5176    -.2647196372    double
>          __powtmp5177    1.225902886    double
>          __powtmp5178    .6666666667    double
>          __powtmp5179    5.563024167e-309    double
>          __powtmp5180    3.613877664e-308    double
>          __powtmp5181    1.424047271e-305    double
>          __powtmp5182    0    double
>          __powtmp5183    2.125183105    double
>          __powtmp5184    3.124453764e-307    double
>          __powtmp5185    2.769750648e+266    double
>          __powtmp5186    1.700051445e-313    double
>          __powtmp5187    2.826759824e-307    double
>          __powtmp5188    1.447097644e-305    double
>          __powtmp5189    1.295163447e-318    double
>          __powtmp5190    1.447097644e-305    double
> etc.
> 
> How can I remove these? I do not need to see them.
> 

If you are using mago as the debug engine (either by explicitly selecting it or via the debugger plugin; the source language in the call stack displays "D" in both cases), then you can disable them being displayed in Tools->Options->Debugger->Mago->Hide compiler generated symbols.
December 30, 2017

On 29.12.2017 13:05, Amorphorious wrote:
> Also, tuple display is quite verbose, can it be removed too?
> 
> 
> +        [0]    {__expand_field_0=-.08063807692, __expand_field_1=.4066909153, __expand_field_2=.91}    std.typecons.Tuple!(double, double, double).Tuple

Currently the field names are always shown.

Even though this looks like a library artefact, it seems the field names are actually compiler generated, too. To the debugger, these are plain structs, but when displaying the single-line "quick-view", the internal names starting with "__" could be hidden, too, while still showing the values.
December 30, 2017

On 29.12.2017 14:46, Amorphorious wrote:
> Also, when I put a BP on an if statement it is not hit and Visual D says that no symbols have been loaded for the document. If I put the BP on a line that isn't an if statement, it hits the BP fine.
> 

I don't think this is a general rule, as it's working most of the time in my experience. I sometimes hit similar issues, but it's usually difficult to reduce them to manageable size.

dmd is sometimes not so great at generating line number info. Can you post an example to bugzilla?