Re: A trace() Christmas gift.
I was unaware that there is a local trace mode as opposed to a global
trace mode.
Regs
Tony
On Sat, 25 Dec 2004 02:14:40 -0800 (PST), guest at rapideuphoria.com
<guest at rapideuphoria.com> wrote:
>
> posted by: a.admin at myway.it
>
> Some tricks that could be not well known and used.
>
> 1. When in the manual trace() mode, you can Double-click any variable name,
> or highlight it with the cursor, if you mind some external delimiter to be
> added,
> then Right-click to copy that string.
>
> 2. after pressing the '?' key for to obtain its value, just Right-click, no
> matter
> where the cursor is, to enter the variable name and press Enter for the
> answer.
>
> 3. It's very easy to copy any text from a DOS window and paste it into an
> editor frame.
> Simply highlight the area you are interested to and Right-click to copy;
> this you can paste where you want.
>
> "Dulcis in fundo"
>
> 4. When in the local trace() mode - that is for instance a trace(2) set inside
> a procedure() -
> you meet the call to another procedure() or function(), this will be silently
> executed,
> without let you see what happened therein.
> To watch these, you should put another trace() command there and so on..
>
> If you set the trace option in your main procedure will trace *everything*,
> once it is turned on, but into a large project this could make "impossible" to
> use it;
> to limit the tracing inside minor routines or loops can sometime drive a
> programmer.. to give up.
>
> Well, put a single trace(1) or trace(2) where you want to start your trip and,
> whenever the cursor
> stands over any routine that you want to explore press Ctrl-Enter; this way
> you can even walk
> through the libraries, if needed.
> Being the real solution to both the above limitations, this new feature makes
> the trace() very powerful.
>
> Merry Christmas to all the Euphorians :o)
>
> Antonio A.
>
>
>
>
--
Regards
Tony Steward
www.locksdownunder.com
IF IT IS TO BE IT IS UP TO ME!
|
Not Categorized, Please Help
|
|
