unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Cc: guile-user@gnu.org, hanwen@cs.uu.nl
Subject: Re: C++ declaration style programming?
Date: Wed, 21 Jan 2004 11:06:24 -0500	[thread overview]
Message-ID: <m3oesx2smh.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <20040121154109.SIFC267436.web02-imail.rogers.com@localhost>

Viktor Pavlenko <vvp@rogers.com> wrote:
> let* is a binding construct by definition and it is an error to
> bind the same identifier twice (r5rs).

Guile complains about duplicate bindings in let or letrec, but not
let*; the second binding simply shadows the first.  I believe that's
what R5RS specifies.  (So it is possible to accidentally shadow an
existing binding, which may cause trouble in subsequent code similar
to set!.)

> Using side effects to re-bind a variable within the binding
> expression of let* sounds like cheating :)

There are other forms of side effects, like I/O.


paul


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2004-01-21 16:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 15:41 C++ declaration style programming? Viktor Pavlenko
2004-01-21 16:06 ` Paul Jarc [this message]
2004-01-22  2:24 ` Thien-Thi Nguyen
2004-01-22  4:28   ` Viktor Pavlenko
  -- strict thread matches above, loose matches on Subject: below --
2004-01-21 14:22 Viktor Pavlenko
2004-01-21 14:26 ` Han-Wen Nienhuys
2004-01-20 22:17 Han-Wen Nienhuys
2004-01-21  3:58 ` Viktor Pavlenko
2004-01-21 12:40   ` Han-Wen Nienhuys
2004-01-21  4:57 ` Issac Trotts
2004-01-21  5:00 ` Stephen Compall
2004-01-21 12:45   ` Han-Wen Nienhuys
2004-01-21  5:03 ` Lynn Winebarger
2004-01-21 21:46 ` Keith Wright

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=m3oesx2smh.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    --cc=guile-user@gnu.org \
    --cc=hanwen@cs.uu.nl \
    /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).