1. OOEU Tracing
- Posted by Matt Lewis <matthewwalkerlewis at yahoo.com> Dec 15, 2004
- 487 views
One thing I forgot to document is that you can set and remove breakpoints anywhere in the code (where "with trace" is in effect). Just click on the line number, and the background will turn red. Click again, and you've removed the break point (background goes back to white). Matt Lewis
2. Re: OOEU Tracing
- Posted by Pete Lomax <petelomax at blueyonder.co.uk> Dec 16, 2004
- 486 views
On Tue, 14 Dec 2004 17:45:57 -0800, Matt Lewis <guest at RapidEuphoria.com> wrote: >One thing I forgot to document is that you can set and remove breakpoints >anywhere in the code (where "with trace" is in effect). Just click on >the line number, and the background will turn red. Click again, and >you've removed the break point (background goes back to white). I can't get trace to work at all on 1.1. opSTARTLINE() only contains code for trace(3) handling in the version I have. BTW, Elliott Sales de Andrade sent me a version with some machine code (apparently based on your fptr.e) which allows unlimited call-backs. Elliott expects there are a few bugs remaining in it. I've uploaded it to my page, along with ooeu 1.1: http://palacebuilders.pwp.blueyonder.co.uk/pdeuex.htm Also, just an idea, your callback.e would probably parse a tad faster if you made sure the 2nd, 3rd, and last characters were more unique (see hashfn() in symtab.e), eg c01_callback_0 c02_callback_0 .. c50_callback_9 It takes my sorry machine 28 seconds to parse those 500 functions! Regards, Pete
3. Re: OOEU Tracing
- Posted by Matt Lewis <matthewwalkerlewis at yahoo.com> Dec 16, 2004
- 480 views
Pete Lomax wrote: > > On Tue, 14 Dec 2004 17:45:57 -0800, Matt Lewis > <guest at RapidEuphoria.com> wrote: > > >One thing I forgot to document is that you can set and remove breakpoints > >anywhere in the code (where "with trace" is in effect). Just click on > >the line number, and the background will turn red. Click again, and > >you've removed the break point (background goes back to white). > > I can't get trace to work at all on 1.1. opSTARTLINE() only contains > code for trace(3) handling in the version I have. Yes, my bad. :( > BTW, Elliott Sales de Andrade sent me a version with some machine code > (apparently based on your fptr.e) which allows unlimited call-backs. > Elliott expects there are a few bugs remaining in it. I've uploaded it > to my page, along with ooeu 1.1: > > <a > href="http://palacebuilders.pwp.blueyonder.co.uk/pdeuex.htm">http://palacebuilders.pwp.blueyonder.co.uk/pdeuex.htm</a> > > Also, just an idea, your callback.e would probably parse a tad faster > if you made sure the 2nd, 3rd, and last characters were more unique > (see hashfn() in symtab.e), eg It's not documented, but that file was generated by make_callbacks.exw. Try changing that and regenerating callback.e, and let me know. In the meantime, I'll take a look at what Eliot's done. Matt Lewis