From: Christopher Lam <christopher.lck@gmail.com>
To: Massimiliano Gubinelli <m.gubinelli@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Unbound variable warning/exception
Date: Sat, 19 Dec 2020 21:07:22 +0800 [thread overview]
Message-ID: <CAKVAZZKmaS_EU6NJEUyGa1CMGK+fjDRbr4V_nHo+D7DEaTqaZw@mail.gmail.com> (raw)
In-Reply-To: <D02A47A9-F788-4E23-9EF3-25E577E04063@gmail.com>
You can remove these "possibly unbound variable" warning by using modules
appropriately. It's not easy and tedious but necessary to achieve better
module hygiene.
See changes in https://github.com/Gnucash/gnucash/pull/831
On Sat, 19 Dec 2020, 6:08 pm Massimiliano Gubinelli, <m.gubinelli@gmail.com>
wrote:
> Hi all,
>
> nice piece of code!
>
> About these "possible unbounded variable" warnings, I have for GNU TeXmacs
> the opposite need: how can I turn them off? :)
>
> I was also curious to ask: which are currently the major applications of
> GNU Guile (as extension language)? For example, in TeXmacs we have ~110.000
> lines of scheme (still Guile 1.8). I wanted to give a look around to
> understand what are good design patterns to use Guile 2+ as extension
> language.
>
> Best,
> Massimiliano
>
> > On 19. Dec 2020, at 02:46, Aleix Conchillo Flaqué <aconchillo@gmail.com>
> wrote:
> >
> > On Fri, Dec 18, 2020 at 5:26 PM Christopher Lam
> > <christopher.lck@gmail.com> wrote:
> >>
> >> Hi guilers, I saw in guix the incredibly useful unbound-variable
> exception
> >> printer written by Ludovic. I've adapted for use in gnucash as
> >> https://github.com/Gnucash/gnucash/commit/6f951784 -- there are now in
> >> guile 3.0.4 many more unbound-var warnings than in 3.0.2 -- wouldn't it
> be
> >> a useful hint to add to the warning in core guile as well?
> >
> > Wow, this is great!
> >
> > This should definitely be added to guile by default.
> >
> > Aleix
> >
>
>
next prev parent reply other threads:[~2020-12-19 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 1:25 Unbound variable warning/exception Christopher Lam
2020-12-19 1:46 ` Aleix Conchillo Flaqué
2020-12-19 10:08 ` Massimiliano Gubinelli
2020-12-19 13:07 ` Christopher Lam [this message]
2020-12-19 16:30 ` Massimiliano Gubinelli
2020-12-20 21:36 ` Ludovic Courtès
2020-12-20 23:11 ` Christopher Lam
2020-12-21 10:48 ` Jérémy Korwin-Zmijowski
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKVAZZKmaS_EU6NJEUyGa1CMGK+fjDRbr4V_nHo+D7DEaTqaZw@mail.gmail.com \
--to=christopher.lck@gmail.com \
--cc=guile-user@gnu.org \
--cc=m.gubinelli@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).