unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Hartwig <mandyke@gmail.com>
To: Patrick Pan <pyxchina92929@gmail.com>
Cc: 13904@debbugs.gnu.org
Subject: bug#13904: A bug in guile's newest documentation.
Date: Sat, 9 Mar 2013 08:52:06 +0800	[thread overview]
Message-ID: <CAN3veRemeNn2Hv1=HeHzcm-zoag0Ug6oXNnMoJnoHsw7MswDbg@mail.gmail.com> (raw)
In-Reply-To: <CANJ3EgHSqzCj3YwPcAhLAiaiqMwDsc+VdeTNQQzcrX4YzkcLAA@mail.gmail.com>

Hello

On 8 March 2013 16:39, Patrick Pan <pyxchina92929@gmail.com> wrote:
> 6.9.8 Procedures with Setters
>
> A procedure with setter is a special kind of procedure which normally
> behaves like any
> accessor procedure, that is a procedure which accesses a data
> structure. The difference is
> that this kind of procedure has a so-called setter attached, which is
> a procedure for storing
> something into a data structure.
> Procedures with setters are treated specially when the procedure
> appears in the special
> form set! (REFFIXME). How it works is best shown by example.
> Suppose we have a procedure called foo-ref, which accepts two
> arguments, a value of
> type foo and an integer. The procedure returns the value stored at the
> given index in the
> foo object. Let f be a variable containing such a foo data structure.
>
>


> Mind the 'REFFIXME'.

Is that the issue you are reporting?

Marks such as this (e.g. ‘FIXME’, ‘TODO’) appear in many places as a
reminder to fix or work on something in the future.  I suppose in this
case it is to cross-reference with the definition of ‘set!’, which
appears absent except for a brief note under _rnrs base_, and informal
definition in _Hello Scheme!_

Generally, I don't think we also need bug reports to track this.





  reply	other threads:[~2013-03-09  0:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08  8:39 bug#13904: A bug in guile's newest documentation Patrick Pan
2013-03-09  0:52 ` Daniel Hartwig [this message]
2013-03-09 11:24   ` Andy Wingo
2013-03-09 13:16     ` Patrick Pan

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='CAN3veRemeNn2Hv1=HeHzcm-zoag0Ug6oXNnMoJnoHsw7MswDbg@mail.gmail.com' \
    --to=mandyke@gmail.com \
    --cc=13904@debbugs.gnu.org \
    --cc=pyxchina92929@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).