From: Richard Todd <rwtodd@mac.com>
Cc: Richard Todd <rwtodd@mac.com>
Subject: [patch] int -> size_t build correction
Date: Tue, 24 Aug 2004 21:05:43 -0500 [thread overview]
Message-ID: <4570750A-F63B-11D8-8679-000A95B4C7DC@mac.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 322 bytes --]
CVS guile doesn't build cleanly for me right now, because of some
'int's in srfi-13.c where size_t's were expected. A patch is attached.
I glanced through the code and didn't see anywhere where it would
depend on those variables being signed, and 'make check' passes for me,
so I think it's good.
thanks,
Richard
[-- Attachment #2: size_t.patch --]
[-- Type: application/octet-stream, Size: 1360 bytes --]
Index: guile-core/libguile/srfi-13.c
===================================================================
RCS file: /cvsroot/guile/guile/guile-core/libguile/srfi-13.c,v
retrieving revision 1.1
diff -u -r1.1 srfi-13.c
--- guile-core/libguile/srfi-13.c 24 Aug 2004 22:11:35 -0000 1.1
+++ guile-core/libguile/srfi-13.c 25 Aug 2004 01:52:18 -0000
@@ -92,7 +92,7 @@
#define FUNC_NAME s_scm_string_any
{
const char *cstr;
- int cstart, cend;
+ size_t cstart, cend;
SCM res;
MY_VALIDATE_SUBSTRING_SPEC_COPY (2, s, cstr,
@@ -151,7 +151,7 @@
#define FUNC_NAME s_scm_string_every
{
const char *cstr;
- int cstart, cend;
+ size_t cstart, cend;
SCM res;
MY_VALIDATE_SUBSTRING_SPEC_COPY (2, s, cstr,
@@ -235,7 +235,7 @@
#define FUNC_NAME s_scm_substring_to_list
{
const char *cstr;
- int cstart, cend;
+ size_t cstart, cend;
SCM result = SCM_EOL;
MY_VALIDATE_SUBSTRING_SPEC_COPY (1, str, cstr,
@@ -763,7 +763,7 @@
#define FUNC_NAME s_scm_string_trim_right
{
const char *cstr;
- int cstart, cend;
+ size_t cstart, cend;
MY_VALIDATE_SUBSTRING_SPEC_COPY (1, s, cstr,
3, start, cstart,
@@ -3001,7 +3001,7 @@
const char *cs;
size_t ctstart, csfrom, csto, cstart, cend;
SCM dummy = SCM_UNDEFINED;
- int cdummy;
+ size_t cdummy;
MY_VALIDATE_SUBSTRING_SPEC (1, target,
2, tstart, ctstart,
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2004-08-25 2:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4570750A-F63B-11D8-8679-000A95B4C7DC@mac.com \
--to=rwtodd@mac.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).