|
PureBytes Links
Trading Reference Links
|
On Tue, 4 May 1999, Howard Jackson wrote:
> 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.
I use the commentary quite a lot, but I would not call it a debugger. One
cannot see variables that well. In fact, to see anything, you must insert
and debug code to get the commentary to work. If one is trying to debug a
long and complex study, the addition of this code is *not* trivial, and
certainly not "Easy" (as in Easy Language :-). If the study is long, there
is a good chance that this extra code will put you over the 64k limit, too
- I've had that happen too many times.
When you have a few loops through 200 or so steps, it becomes quite
cumbersome to use the commentary. One cannot 'step over' chunks of code,
set variables, or do many of the things that a debugger would do. In
short, it has few of the capabilities of a real debugger. It is simply one
more work-around to overcome the deficiencies of TS.
Also, if you use the commentary as part of the study, one cannot use it as
a debugger too. Since I do use it in some of my studies, this is a *big*
problem.
I don't like to focus on problems so much either. It is just that there
are so many, and they occur so often for a supposedly "mission-critical"
program that people use to make a living. It should, and could, be better.
A real debugger would get us out of the dark ages...
Larry
|