Especially given the presence of John R on this forum, I have a somewhat technical question - mainly for my own understanding but hopefully it would be useful in practice as well.
In order for CAV and IAV to function from the toolbar during debugging, it is (presumably) necessary for CVF/IVF to have the "inquiry" capability to get the address of a highlighted array in the debugger, and (probably) its type and dimensions. Then it can be sent to the CAV/IAV engines, etc.
Is this "inquiry" functionality supported by VS itself, or was it something that Compaq/Intel had to develop as part of a plugin?
As well as curiosity-driven, I am developing some auxiliary debugging tools (I am currently doing some fairly heavy numerical work and got tired of copy/pasting or write/reading many large matrices to inspect their properties). These tools are almost done now, but I would like to go one step further and be able to invoke them via toolbar macros, etc. For this I would need to get things like address (and maybe dimensions) from a macro-like script.
I did get a "not possible" from Steve in an earlier related post, but would at least like to understand (broadly) why not, and (also broadly) how was a similar functionality achieved for CAV/IAV.
There was also a promising suggestion by Lorry M to use "out-of-line" calls (which would have done the job perfectly) but unfortunately it was only for C/C++ and not for Fortran.. But what I am asking here is (maybe) easier than out-of-line calls - I dont want to call any user-supplied procedures, just get some (existing) information.
thanks in advance for any insights, even if they may not change the final verdict..
PS: Jim Dempsey's suggestion (http://software.intel.com/en-us/forums/showthread.php?t=67398) regarding using IAV to monitor arrays during program execution is excellent, and I am starting to adopt it for dynamic visualization of output and internal variables. It is indeed very powerful for that purpose.
But in my debugging context its not quite as convenient (unless I mis-understood something) because it would require to compute all potential properties of interest. This is certainly possible but expensive and a bit inflexible. Ideally I would like the capability to pick the specific array (and the specific property to compute) during the debug and analyse it separately. Evidently this requires some similar inquiry functionality to what CAV and IAV need and were able to achieve, hence my post..