From: Andrea Crotti <andrea.crotti.0@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: dired.c
Date: Tue, 26 Apr 2011 13:58:30 +0200 [thread overview]
Message-ID: <sa0r58pjkbd.fsf@gmail.com> (raw)
In-Reply-To: <jwvbozu1meq.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> Actually, IIUC we could move it all to eval.c.
>
>
> Stefan
I just tried out what you suggested and it compiles to me with these changes:
(sorry it's not a right bzr patch format I still have to check how to do it)
crotti@plaetekopp:~/trunk$ bzr diff src/lisp.h
=== modified file 'src/lisp.h'
--- src/lisp.h 2011-04-15 08:22:34 +0000
+++ src/lisp.h 2011-04-26 11:51:36 +0000
@@ -1966,40 +1966,6 @@
struct handler *next;
};
-/* This structure helps implement the `catch' and `throw' control
- structure. A struct catchtag contains all the information needed
- to restore the state of the interpreter after a non-local jump.
-
- Handlers for error conditions (represented by `struct handler'
- structures) just point to a catch tag to do the cleanup required
- for their jumps.
-
- catchtag structures are chained together in the C calling stack;
- the `next' member points to the next outer catchtag.
-
- A call like (throw TAG VAL) searches for a catchtag whose `tag'
- member is TAG, and then unbinds to it. The `val' member is used to
- hold VAL while the stack is unwound; `val' is returned as the value
- of the catch form.
-
- All the other members are concerned with restoring the interpreter
- state. */
-
-struct catchtag
-{
- Lisp_Object tag;
- Lisp_Object val;
- struct catchtag *next;
- struct gcpro *gcpro;
- jmp_buf jmp;
- struct backtrace *backlist;
- struct handler *handlerlist;
- int lisp_eval_depth;
- int pdlcount;
- int poll_suppress_count;
- int interrupt_input_blocked;
- struct byte_stack *byte_stack;
-};
extern Lisp_Object memory_signal_data;
crotti@plaetekopp:~/trunk$ bzr diff src/dired.c
=== modified file 'src/dired.c'
--- src/dired.c 2011-04-14 19:34:42 +0000
+++ src/dired.c 2011-04-26 11:51:08 +0000
@@ -22,7 +22,7 @@
#include <stdio.h>
#include <sys/types.h>
#include <sys/stat.h>
-#include <setjmp.h>
+/* #include <setjmp.h> */
#ifdef HAVE_PWD_H
#include <pwd.h>
--
GNU Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.22.0)
of 2011-03-04 on plaetekopp
next prev parent reply other threads:[~2011-04-26 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 8:57 dired.c Andrea Crotti
2011-04-25 6:08 ` dired.c Paul Eggert
2011-04-25 6:50 ` dired.c Eli Zaretskii
2011-04-25 13:40 ` dired.c Stefan Monnier
2011-04-26 11:58 ` Andrea Crotti [this message]
2011-05-04 19:53 ` dired.c Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=sa0r58pjkbd.fsf@gmail.com \
--to=andrea.crotti.0@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.