From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Gerd Moellmann <gerd@gnu.org>, 75451@debbugs.gnu.org
Subject: bug#75451: scratch/igc: Enable CHECK_STRUCTS
Date: Thu, 09 Jan 2025 06:09:35 +0100 [thread overview]
Message-ID: <m2v7uoo9o0.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkmnSngLQg7sLdjZMYe9i14McUawAm=ns+o1_nqFkH98oPg@mail.gmail.com> (Stefan Kangas's message of "Wed, 8 Jan 2025 21:57:06 -0600")
Stefan Kangas <stefankangas@gmail.com> writes:
> Severity: wishlist
>
> Gerd, how do you feel about the below change? There's no rush to make
> this change if it's inconvenient for you, but since you use IN_MY_FORK
> elsewhere, I figured that it might be okay for you here also?
>
> If it's too much trouble, let's just revisit this later. This bug
> report will serve as a reminder, if we just lave it open.
>
> diff --git a/src/igc.c b/src/igc.c
> index 079b6a90ac6..b03c64a52b8 100644
> --- a/src/igc.c
> +++ b/src/igc.c
> @@ -76,8 +76,7 @@
> # error "HAVE_PDUMPER required"
> #endif
>
> -#if 0 /* Not yet because that make transfer between GNU and my fork
> - painful. */
> +#ifndef IN_MY_FORK
> #ifdef CHECK_STRUCTS
> # include "dmpstruct.h"
No no, it's no trouble. Thanks for working on this!
I'd even go a step further and remove the whole #if. I think it's more
useful nowadays to have the checks than to make patching easier. (BTW,
the contents of the #if might be out of date, not sure if we meanwhile
fix/scan additional structs.)
next prev parent reply other threads:[~2025-01-09 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 3:57 bug#75451: scratch/igc: Enable CHECK_STRUCTS Stefan Kangas
2025-01-09 5:09 ` Gerd Möllmann [this message]
2025-01-09 7:20 ` Stefan Kangas
2025-01-09 7:25 ` Gerd Möllmann
2025-01-09 10:09 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 12:44 ` Stefan Kangas
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=m2v7uoo9o0.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=75451@debbugs.gnu.org \
--cc=gerd@gnu.org \
--cc=stefankangas@gmail.com \
/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.