Re: LYNX-DEV FIX: debugging that URL...

[Filip M Gieszczykiewicz]

You (Foteos Macrides) wrote:
> It's a judgement call.  That function is called from a zillion
> places, and should never be called with a bad pointer.  It can't return
> an error value.  That -1 implies a valid comparison to the calling
> function, which will continue on that basis, and probably to something
> strange.  The function doesn't know what called it, so a TRACE message
> can't report that.  By letting it crash, on VMS the fatal error routine
> includes a TRACEBACK, which includes the sequence of calling functions,
> and other useful information.  So I was able to debug it literally in
> less than a minute.  It could take hours to figure out why strange
> behavior is occurring if it returned a false but seemingly valid value,
> or it might be valid by chance, making it even more likely that
> blatantly bad code could look OK and get out the door.

Greetings. See what happens when I try to actually fix something in
lynx? I fall flat on my face ;-) I understand... just have no clue
of why lynx does what it does when and how. But you can feel free to
trust me with your bookmarks.... [smirk]

:-)

Take care.
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;