From: philip@warpmail.net (Philip K.)
To: Mark H Weaver <mhw@netris.org>
Cc: guile-user@gnu.org
Subject: Re: Weird Guile Scheme Behaviour
Date: Wed, 16 Oct 2019 09:48:47 +0200 [thread overview]
Message-ID: <87eezdb068.fsf@bulbul> (raw)
In-Reply-To: <87sgntqj0l.fsf@netris.org> (Mark H. Weaver's message of "Wed, 16 Oct 2019 02:52:15 -0400")
[-- Attachment #1: Type: text/plain, Size: 557 bytes --]
Mark H Weaver <mhw@netris.org> writes:
> The problem here is that '(start) is a *literal* list, and it's an error
> to modify literals in Scheme. In other words, modifying a literal
> results in undefined behavior. Like C string literals, Scheme literals
> are actually part of the program text itself.
Ah, that makes sense. I totally forgot about the difference between
'(start) and (list 'start).
> Regards,
> Mark
Thanks a lot for your response, helped my clear up understanding.
--
With kind regards,
Philip K.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2019-10-16 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 9:43 Weird Guile Scheme Behaviour Philip K.
2019-09-13 12:43 ` Neil Jerram
2019-09-13 17:22 ` Vladimir Zhbanov
2019-10-16 6:52 ` Mark H Weaver
2019-10-16 7:48 ` Philip K. [this message]
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=87eezdb068.fsf@bulbul \
--to=philip@warpmail.net \
--cc=guile-user@gnu.org \
--cc=mhw@netris.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).