OpenEuphoria

Re: CLARIFYING TRACE COMMAND

• Posted by Pete Lomax <petelomax at blueyonder.co.uk> Mar 16, 2003
• 425 views

On Fri, 14 Mar 2003 11:18:50 -0500, Bernie Ryan
<xotron at bluefrognet.net> wrote:

>I don't know if everyone really understood the great
>NEW feature of trace.
>
>If you are on a trace screen and a you have a long sequence already
>displayed on the screen like this:
>s =3D {12344, 23345, 3444, 33990, ...
>and you want to view the whole sequence do the following:
>Press the question mark command ( ? ) then ask trace to display
>sequence s again. The display screen will then go into a
>display mode allowing you to view the complete sequence.
>
>GOOD JOB ROB !
>
Is there any way to change the trace pretty print mode?.
eg in misc.e
	-- set option defaults=20
	pretty_ascii =3D 1		   --[1]=20

I've tried changing that to 2, to no effect. I do suspect I'm pushing
my luck to expect that to work inside the trace window...

On a related note, I have changed database.e as follows:
		pretty_print(fn, key, {2, 2, 8})	--PL was 1,2,8
		pretty_print(fn, data, {2, 2, 9})	--PL was 1,2,9
It would be nice if db_dump's second parameter was an object; if
integer behave as now else allow a sequence to define several
different options, in my case the pretty print format would be one of
them.

It is also a little confusing that dbdump() shows the version of the
database as created, but not the version of the current running
software.

When viewing the trace, it would also be rather nice to be able to
cursor back up a large structure.

Pete