Hi Karl and Chuck
Well, it turns out that part two of my message was a false alarm.
Reformatting does not have a mysterious effect on parsing after all, I
just had a confounding variable at the same time. Anyway,
the incorporation of the python beautifier, in the first place, is the
real news! There is indeed a coherent change in the line number for the
bug I was describing, from
$(..) in line 1
to something like
$(..) in line 5017
That's what I was hoping for - I'm still someplace in the middle with
fastmail, but making extra progress as a result of the line numbers!
Course I would expect a syntax error, not a type error.
Yes, it may be one of those things where the reported cause for runtimes
is skewed relative to what is actually going on. As a matter of fact, I
was thinking recently that when I sit down with pages' worth of edbrowse
output from the higher debug levels, I am generally starting at the
bottom, which may be a mistake. It suddenly hit me that runtimes in these
web pages may be a little like the compilation errors from gcc or
something! Maybe there is a cascading effect, and the errors lower down
are side effects of the first few. So I should be going to the root cause
and starting with the first thing first. I discovered that it makes a
nice debug mode if I add some exit(0) statements to readMessage in ebjs.c.
So this way, the whole program will quit on the very first error, which
forces me to address things in the order they occur.
K
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
