in the locals window:
types seem to work for: static arrays, scalars, structs.
types are wrong for: strings, associative arrays, dynamic arrays. Classes show as struct*.
Is this something you have control over, or does that depend on monodevelop? Where are the relevant functions one would need to modify in github source code?
In the meantime, before all this gets fixed, what I really miss is ability to call a function directly, which would allow to circumvent bugs in display of variables, etc, and also allow for convenient exploratory programming. It is possible to some extent in visuald D (see my post: http://forum.dlang.org/thread/poefipvtjbcpnkopktja@forum.dlang.org, calling a function inside visual D debugger: partially possible, want better support), and in lldb and gdb.
how much of these debugging capabilities are shared between windows and linux?
in the locals window: types seem to work for: static arrays, scalars, structs. types are wrong for: strings, associative arrays, dynamic arrays. Classes show as struct*.
Is this something you have control over, or does that depend on monodevelop? Where are the relevant functions one would need to modify in github source code?
In the meantime, before all this gets fixed, what I really miss is ability to call a function directly, which would allow to circumvent bugs in display of variables, etc, and also allow for convenient exploratory programming. It is possible to some extent in visuald D (see my post: http://forum.dlang.org/thread/poefipvtjbcpnkopktja@forum.dlang.org, calling a function inside visual D debugger: partially possible, want better support), and in lldb and gdb.
how much of these debugging capabilities are shared between windows and linux?