retrieve variables from workspace that is being debugged

I'm writing some code that is meant to provide information about code I am writing, including when not running (file or base workspace analysis) AND when debugging. This is sort of like the workspace browser in that when debugging, the workspace browser let's you know what variables are defined in your current workspace (and provides that information to you to help write future code). Is it possible to achieve anything similar to the workspace browser programmatically? My "analysis" code would be running periodically via a timer with no obvious connection to the code being debugged.

[Geoff Hayes]

Jim - are you suggesting that you would like to have some code read your code (function or script) and (say) list all of the variables in that piece of code?

[Jim Hokanson]

That is correct, although I'd like to have type and size information as well, not just the name (i.e. the information that the workspace viewer has). This would preferably be during debugging, although I'm planning on starting some preliminary static analysis (file prior to execution) based on mlintmex. Suggestions on that are welcome.