> > > http://www.fltk.org/str.php?L2158=3D20
> > It took me weeks of debugging to come up with that one line fix!
> And a very lovely fix it is too.
>
> Also: You do realise, having found this bug, that this probably makes
> you *the* expert on fixing bugs in Fl_Text_Editor now...
Please don't joke about such things :-) In another thread I said:
" ... good luck debugging FL_Text_Display and internals, as
this has to be some of the most obscure recursive code I've
ever seen."
it took me a few revisions to come up with such a neutral comment.
I found it two weeks of really hard slog debugging using printf!
I don't believe that mere mortals have much chance of understanding
that code. There's far too much recursion, repeated loops and blocks
of code that look similar but in fact have subtle changes or extra
tests. Too many things are done 'on-the-fly' so you have to step in
to the recursive routines to discover the return values that are
then passed immediately as function parameters, etc.
But if I remember correctly, the worst thing about the code is the
terminology used, both inappropriate nouns and verbs, and then the
mixing of "similar" terms (eg. length, chars, width, measure, pixels)
IMHO, the code as it stands is a maintenance black hole, but for
someone to recode the same functionality from scratch is non-trivial.
I'm sorry if I'm going to offend anyone who worked on the code by
saying this, but this is a "the Emperor has no clothes" moment!
Cheers
D
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
