unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Rouben Rostamian" <rostamian@umbc.edu>
Subject: garbled documentation
Date: Wed, 31 Dec 2003 13:25:11 -0500	[thread overview]
Message-ID: <200312311825.hBVIPB42016073@pc18.math.umbc.edu> (raw)

I hope that this bug report is addressed to the right place.  Please
let me know if it is otherwise.

Version: guile--1.6.4
  Guile reference manual: both "info" and TeX formats:
    In the section titled "Bit Vectors":

In the description of bit-set*! we read:

 - Scheme Procedure: bit-set*! v kv obj
 - C Function: scm_bit_set_star_x (v, kv, obj)
     If uve is a bit-vector BV and uve must be of the same length.  If
     BOOL is `#t', uve is OR'ed into BV; If BOOL is `#f', the inversion
     of uve is AND'ed into BV.

     If uve is a unsigned long integer vector all the elements of uve
     must be between 0 and the `length' of BV.  The bits of BV
     corresponding to the indexes in uve are set to BOOL.  The return
     value is unspecified.

This description is garbled.  The procedure arguments are listed
as "v kv obj" while the description refers to "uve, BV, BOOL", etc.

In fact, most descriptions under the section "Bit Vectors" suffer from
the same problem.

-- 
Rouben Rostamian


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile


             reply	other threads:[~2003-12-31 18:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 18:25 Rouben Rostamian [this message]
2004-01-08 22:06 ` garbled documentation Kevin Ryde

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=200312311825.hBVIPB42016073@pc18.math.umbc.edu \
    --to=rostamian@umbc.edu \
    /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).