>Jos-
>
>>Hi Fabio. I dont use the ASSERT command myself (becuase I write only the most simple "hello world" applications) but I agree with your thinking that a debugger ideally should observe but not influence the application.
>
>As far as I am aware, external debuggers would be able to do this, but not internal debuggers. In other words, it would have to be a debugger that runs in a different process than the application. The FoxPro debugger just isn't that sort of debugger, and the wishing it weren't so won't make it so. Much more sensible to understand what the tool is, and what features help you accomplish the task you need to accomplish. IMNSHO.
I don't deny that understanding "what is" is of practical use and hence my statement "ideally should observe...". I express only what would be ideal, not complain about what is nor wish for something else. Fabio's observation is factually correct. Whether it is worthwhile, or even possible, to change is another matter entirely. IMVHO.
In the End, we will remember not the words of our enemies, but the silence of our friends - Martin Luther King, Jr.