From: Mike Gran <spk121@yahoo.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: apparenty SCM_I_CHAR is fixed, but:
Date: Wed, 19 Aug 2009 08:39:49 -0700 [thread overview]
Message-ID: <1250696389.18373.1098.camel@localhost.localdomain> (raw)
In-Reply-To: <87my5vkeqq.fsf@gnu.org>
On Wed, 2009-08-19 at 17:25 +0200, Ludovic Courtès wrote:
> Mike Gran <spk121@yahoo.com> writes:
> > For gcc, -Wtype-limits will catch this at compile time.
>
> IIUC this is precisely a compile-time warning. :-)
It is a compile time warning that is default for Greg, but apparently
not for Andy or I.
-Mike
prev parent reply other threads:[~2009-08-19 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 13:56 apparenty SCM_I_CHAR is fixed, but: Greg Troxel
2009-08-19 15:09 ` Mike Gran
2009-08-19 15:25 ` Ludovic Courtès
2009-08-19 15:37 ` Greg Troxel
2009-08-19 15:39 ` Mike Gran [this message]
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=1250696389.18373.1098.camel@localhost.localdomain \
--to=spk121@yahoo.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/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).