From: Eric McDonald <mcdonald@phy.cmich.edu>
To: guile-user@gnu.org
Subject: Re: Interesting Behavior of 'append!' In Local Context
Date: Sat, 17 Oct 2009 20:36:41 -0400 [thread overview]
Message-ID: <4ADA6319.1030004@phy.cmich.edu> (raw)
In-Reply-To: <2F77A419-E28E-4936-854C-5FAE76D85815@member.fsf.org>
Stephen Compall wrote:
> Literals are literally literal. That is to say:
>
> (define (itsaliteral) '(42 42))
Thanks, Stephen. I never really looked at quote as declaring a literal.
I primarily saw its use for suppressing evaluation inside the quoted
entity, and as a convenient shorthand for making lists. I guess it's a
convenient shorthand for making _literal_ lists. (And, the Guile
documentation even uses the word literal - now that I'm looking for it. ;-)
> It is an error to modify literals, but it is also not required by R5RS
> to detect and inform of such erroneous modification. It is, however,
Fair enough. I certainly wouldn't mind seeing "detect and inform"
implemented for this case. As a comparison: if I'm writing C or C++
code, and I try to modify a const value, the compiler is generally going
to let me know.
Anyway, sorry to trouble the list with a noobish oversight.
Regards,
Eric
next prev parent reply other threads:[~2009-10-18 0:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 22:28 Interesting Behavior of 'append!' In Local Context Eric McDonald
2009-10-17 23:09 ` Stephen Compall
2009-10-18 0:36 ` Eric McDonald [this message]
2009-10-18 1:45 ` Stephen Compall
2009-10-18 13:53 ` Eric McDonald
2009-10-18 10:25 ` Andy Wingo
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=4ADA6319.1030004@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=guile-user@gnu.org \
/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).