Re: How to see internal calculations in EL

[Howard Jackson <hrjf4@xxxxxxxxx>]

There is a built in step by step (or bar by bar in our
case) debugger facility for EasyLanguage.    I'm
getting very tired of most of you just focusing on the
problems and the negative and not even trying to find
solutions.

Have you guys ever taken a look at how the expert
commentary works?   I did.    If you click on any bar
with the commentary icon, you will get some text
dumped into a window for that specific bar.   Does it
have to be the commentary explaining market
conditions? NO!!!

If you write a simple ShowMe or indicator like:

condition1 = close > open;
If condition1 then
   plot1(High,"x")
else
   plot1(low,"x");
commentary("My condition is:", condition1);


Then you apply this to a chart, go ahead and click on
the expert commentary window and then on any bar of
the chart.   You now have a step debugger that will
allow you to see what state anything is on any bar by
just clicking on the bar you want your data in.

I believe some months back someone from Omega had a
big post on using the commentary.  Anyone care to
check the archives?

H 

--- Chris Baker <chrisbak@xxxxxxxxx> wrote:
> -----Original Message-----
> From: William R Wood <wr_wood@xxxxxxxxxxxxx>
> To: Omega Email List <omega-list@xxxxxxxxxx>
> Date: Tuesday, May 04, 1999 10:24 AM
> Subject: How to see internal calculations in EL
> 
> 
> >But I can't figure out how to see the internal math
> of functions/indicators
> >etc. For example how do you see the changing states
> of conditions that
> >switch from true to false or the results of
> calculations by functions that
> >contribute to the final result but do not get
> plotted.  All I see so far are
> >the final results that get plotted and are thus
> visible in the Data Window
> 
> For a truly "Easy Language" I would have thought
> kind of step-by-step debugger
> program you are expecting would have been part of
> the minimum requirement for TS
> 2000.   However obviously Omega Research, and Omega
> advisors like Pierre
> Orphelin, didn't see it that way.
> 
> As a result to debug Easy Language we are left with
> very primitive techniques.
> I two techniques for debugging: Print statements,
> typically to the print to
> Print Log, and Plot statements.    For example I
> will use a Print statement
> like:
> if Date = 990503 [or other condition] then
> Print(Date:6:0," ",Time:4:0, " ",
> [variables]);
> 
> That means if the Trade Date is 05/03/99 then print
> the to the Print Log:
> Trade Date and Time, in the format yymmdd hhss,
> [followed by variable values].
> 
> Easy Language can be a difficult language to work
> with for those not used to
> such obsolete debugging techniques.   Somehow this
> clear inadequacy in
> TradeStation has never been noticed by reviewers for
> trade magazines, who seem
> clearly more interested in selling magazines than
> pointing out obvious faults in
> products of their advertisers.
> 
>