From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Philipp Stephani
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sun, 22 Nov 2015 09:03:39 +0000
> Cc: aurelien.aptel+emacs@gmail.com, tzz@lifelogs.com, emacs-devel@gnu.org
>
> We have already discussed longjmp at length in this thread, and Daniel= ,
> Aur=C3=A9lien and I are all strongly against it. Using longjmp makes i= t effectively
> impossible to write modules in any language but C, and even C code has= to be
> very careful (e.g. it can't use __attribute__((cleanup))). longjmp= is only
> possible within a monolithic system that is able to make closed-world<= br> > assumptions such as the Emacs binary itself, it is impossible in gener= ic and
> portable library code. We have worked hard to remove the possibility o= f longjmp
> leaking into module code, and I won't put that possibility back in= .
I don't understand: we already have in emacs-module.c machinery that
handles non-local exits.=C2=A0 Why cannot xmalloc do the same when it's=
called from emacs-module.c?