Re: Problems with debug-on-entry in the Lisp debugger.

[Stefan Monnier <monnier@iro.umontreal.ca>]

> I see you implemented this.  This makes debug-on-entry for macros a
> lot better, of course.  Thanks.  But the problem I mentioned remains:
> the debug-entry-code is visible.
[...]
> Debugger entered--entering a function:
> * (lambda (var) (if (or inhibit-debug-on-entry debugger-jumping-flag) nil (debug ...)) (list (quote setq) var (list ... var)))(x)
>   (inc x)
[...]

Other than the aesthetic aspect (which we can fix by just removing the
offending line in an ad-hoc way), does it have any real impact?

> I think the effect on performance will be very minimal.

But I see no compelling reason to pay this price.

After all, we've live for many years with this elisp implementation without
nearly any complaint.  If the aesthetic aspect is just more serious now that
we replace (debug 'debug) with (if (or inhibit-debug-on-entry
debugger-jumping-flag) nil (debug 'debug)), we can define a function named
e.g. `debug-entering' that will do the checking of inhibit-debug-on-entry
and debugger-jumping-flag.


        Stefan