guile-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Guile-commits] GNU Guile branch, master, updated. cabf1b31a3a2c0bdb3a93


From: Neil Jerram
Subject: [Guile-commits] GNU Guile branch, master, updated. cabf1b31a3a2c0bdb3a936ceda86491999b262b1
Date: Fri, 05 Jun 2009 21:55:03 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Guile".

http://git.savannah.gnu.org/cgit/guile.git/commit/?id=cabf1b31a3a2c0bdb3a936ceda86491999b262b1

The branch, master has been updated
       via  cabf1b31a3a2c0bdb3a936ceda86491999b262b1 (commit)
      from  782a82eed13abb64393f7acad92758ae191ce509 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit cabf1b31a3a2c0bdb3a936ceda86491999b262b1
Author: Neil Jerram <address@hidden>
Date:   Fri Jun 5 22:54:45 2009 +0100

    Fix `Mismatching FUNC_NAME' warning from guile-func-name-check
    
    * libguile/bytevectors.c (FUNC_NAME): Change to match function name.

-----------------------------------------------------------------------

Summary of changes:
 libguile/bytevectors.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/libguile/bytevectors.c b/libguile/bytevectors.c
index ced1b08..1de4db0 100644
--- a/libguile/bytevectors.c
+++ b/libguile/bytevectors.c
@@ -577,7 +577,7 @@ SCM_DEFINE (scm_bytevector_u8_set_x, "bytevector-u8-set!", 
3, 0, 0,
 SCM_DEFINE (scm_bytevector_s8_set_x, "bytevector-s8-set!", 3, 0, 0,
            (SCM bv, SCM index, SCM value),
            "Return the octet located at @var{index} in @var{bv}.")
-#define FUNC_NAME s_scm_bytevector_u8_set_x
+#define FUNC_NAME s_scm_bytevector_s8_set_x
 {
   INTEGER_NATIVE_SET (8, signed);
 }


hooks/post-receive
-- 
GNU Guile




reply via email to

[Prev in Thread] Current Thread [Next in Thread]