1. Small parsing bug and more trace suggestions
Here is a minor bug...
-- demo a bug where Eu parsing breaks.
-- If "trace" is coded between the procedure declaration and the
-- first private variables, ie immediately after the proc dcl.
-- error is "Syntax error - expected to see possibly end not a type"
-- Euphoria v2.5
-- workaround is to put the trace(1) after the variables declarations
--
with trace
procedure main()
trace(1)
integer i1
i1 = 0
i1 = i1 + 1
end procedure
main()
How about these two trace options in the trace window:
a) Being able to jump x number of statements and resume trace
b) Specifying a variable name where trace will resume once its referenced.
Will need to specify variable scope though (global/local/private)
Regards
Alan
From BC's "The curse exchange", by Johnny Hart:
"May your only son, the political candidate, be caught in the company of a
nefarious mud wrestler 3 days before the election"
"May the fleas of a thousand camels infest your armpits"
2. Re: Small parsing bug and more trace suggestions
Alan Oxley wrote:
> How about these two trace options in the trace window:
> a) Being able to jump x number of statements and resume trace
> b) Specifying a variable name where trace will resume once its referenced.
> Will need to specify variable scope though (global / local / private)
OK, I'll add them to my list of ideas for trace.
Thanks,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com