From: ludo@gnu.org (Ludovic Courtès)
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] guile: Remove (gdb init) module, and include 'init.scm'.
Date: Sat, 12 Jul 2014 14:55:00 -0000 [thread overview]
Message-ID: <87k37ikb2x.fsf@gnu.org> (raw)
In-Reply-To: <m34myn6vkg.fsf@sspiff.org> (Doug Evans's message of "Fri, 11 Jul 2014 21:38:07 -0700")
Hi, Doug,
Doug Evans <xdje42@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> This patch is a prerequisite for the following (compiling Scheme
>> files). It removes the (gdb init), which had a top-level circular
>> dependency with (gdb), thereby preventing compilation.
>>
>> Thanks,
>> Ludo’.
>>
>> gdb/
>> 2014-06-20 Ludovic Courtès <ludo@gnu.org>
>>
>> * guile/guile.c: (gdbscm_init_module_name): Change to "gdb".
>> * guile/lib/gdb.scm: Remove 'use-modules' form and include
>> gdb/init.scm. Change 're-export' to 'export'. Export
>> '*pretty-printers*' and '%assert-type'.
>> * guile/lib/gdb/init.scm: Remove 'define-module' form.
>> (%exception-print-style): Remove.
>> * guile/lib/gdb/boot.scm: Change (gdb init) to (gdb).
>> * guile/lib/gdb/experimental.scm: Remove use of (gdb init).
>> * guile/lib/gdb/types.scm: Likewise.
>> * guile/lib/gdb/printing.scm: Add '%assert-type', 'SCM_ARG1', and
>> '*pretty-printers*' to the selection.
>
> Hi.
>
> IWBN to not export %assert-type.
> I was also thinking IWBN to not export *pretty-printers* and instead
> export a function that returns the value. WDYT?
I agree, but that was needed for gdb/printing.scm.
That said, we may be able to access them from there using ‘@@’. Perhaps
that’d be preferable. I can try that if you want. WDYT?
> btw, is (include ...) documented anywhere?
Yes (info "(guile) Local Inclusion").
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-07-12 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 21:26 Ludovic Courtès
2014-07-12 5:01 ` Doug Evans
2014-07-12 14:55 ` Ludovic Courtès [this message]
2014-07-12 17:42 ` Doug Evans
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=87k37ikb2x.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox