OpenEuphoria

Re: request for 2.5

• Posted by Pete Lomax <petelomax at blueyonder.co.uk> Oct 15, 2004
• 470 views

On Thu, 14 Oct 2004 08:15:11 -0700, Robert Craig
<guest at RapidEuphoria.com> wrote:

>Why would you want even finer control?.
1) There are *many* times when I study five or six lines in earnest,
then hit return/downarrow a dozen or more times to get round to the
next iteration. Disabling trace on the bottom half of a loop would
often be very useful.

2) I want to see _how_ a routine is called, not what it does. eg:

function getSet(object Type)

	trace(1)
	<some line that the debugger will pause on>
	without trace
	<rest of routine>
end function

It is quite common that the bug is not in the routine, but how it is
called, or how the (valid) results are being handled.

What would be nice is F9 to run to the end of the current routine. 

2) I've entered a routine I'm not interested in, eg

	Update(All,getSet(Type))

Now, I want to see what happens in Update, but I don't want to run
through what getSet() is doing. Maybe I could without trace around the
getSet routine, maybe sometime later I will want to trace through it.
Maybe I've already spent five minutes in the debugger.
One thing that would be nice is F10 to simply switch off all tracing
of the current routine, for this session. To make that permanent, then
obviously I put without trace/with trace around that routine, before I
next run the program. If it is easier for F10 to switch off just the
current line, that would be good too. Maybe a small undo buffer, but
otherwise once it is switched off, that's it this session.
I'm sure you understand that trace(1) at the start of Update() might
trigger thousands of times before the point of interest, and indeed
that some of the variables I want to test might be out of scope.

Regards,
Pete
PS Feel free to replace F9/F10 with any keystroke of your choice.