Re: Attaching context info to an error

[Alan Mackenzie <acm@muc.de>]

Hello, João.

On Fri, Dec 29, 2023 at 17:54:30 +0000, João Távora wrote:
> On Fri, Dec 29, 2023 at 5:43 PM Alan Mackenzie <acm@muc.de> wrote:

> > > It's a similar object with a unique type.

> > Similar to what?

> The object that signal() would craft and appear to Lisp is similar to how
> symbol-with-pos is passed to, say, compiler macros (breaking some of
> them, last I remember, but that's besides our discussion).

Ah, right!  So you're considering, possibly, a new type of pseudovector,
or something similar.

> > > So it's going to need more arguments than just being scared of generic
> > > functions.

> > There's no fear involved at all.  cl-lib is an exceptionally
> > controversial part of Emacs, as we established two or three weeks ago.
> > It's poorly documented, and likely buggy.  It's not something to be
> > moved to the centre of the Emacs Lisp machine.

> generic functions aren't in cl-lib, and, once again, noone is proposing
> doing anything of the sort, so why you bring cl-lib up is mystery to me.

The word "generic" was mentioned, which makes me think of cl-generic.el,
a file I'm struggling quite badly with, to debug.  By cl-lib, I meant
cl-*.el.  Sorry for not being more exact.

> > > Noone is advocating for calling generic functions from C or preloading
> > > them, etc, so don't worry about it.

> > That's got no connection with what I wrote.  What I'm asking you to
> > confirm is that you're not contemplating introducing error handling
> > machinery which, during bootstrap, will only work after Lisp code has
> > been loaded.

> I think I can confirm that yes.

Thanks!

> João

-- 
Alan Mackenzie (Nuremberg, Germany).