From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: guile-user@gnu.org
Subject: Re: C++ declaration style programming?
Date: Wed, 21 Jan 2004 13:40:42 +0100 [thread overview]
Message-ID: <16398.29514.719974.994390@localhost.localdomain> (raw)
In-Reply-To: <16397.63705.338864.586672@shmyh.ua>
vvp@rogers.com writes:
>
> (let* ((var1 (+ (something) 2))
> (var2 (+ (something var1) var1))
> (var3 (something var1 var2)))
>
> If you need to change var3 at a later point, just give it another name:
>
> (let ((var3-2 (+ (something-else var3))))
> (...
>
> instead of set!-ting it. The problem with set! in a lexically scoped
> language is that you can change the binding of a variable defined at a
> higher level by mistake:
I know about all this. The example was a little contrived. The things
I have in mind are statements which currently return SCM_UNSPECIFIED.
I think it looks stupid to do
(let* ((a (something))
(unused (display a))
(b (something-else a))
..
)
which introduces a variable unused, and puts emphasis on the
declaration, not on the main action of the statements.
--
Han-Wen Nienhuys | hanwen@xs4all.nl | http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-01-21 12:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 22:17 C++ declaration style programming? Han-Wen Nienhuys
2004-01-21 3:58 ` Viktor Pavlenko
2004-01-21 12:40 ` Han-Wen Nienhuys [this message]
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
-- 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-21 15:41 Viktor Pavlenko
2004-01-21 16:06 ` Paul Jarc
2004-01-22 2:24 ` Thien-Thi Nguyen
2004-01-22 4:28 ` Viktor Pavlenko
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=16398.29514.719974.994390@localhost.localdomain \
--to=hanwen@xs4all.nl \
--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).