From: Arne Babenhauserheide <arne_bab-S0/GAf8tV78@public.gmane.org>
To: Alan Manuel Gloria <almkglor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: guile-user-mXXj517/zsQ@public.gmane.org,
readable-discuss
<readable-discuss-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Matt Wette <matt.wette-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: wisp literal array syntax for Guile, a good idea?
Date: Wed, 13 Dec 2017 18:29:33 +0100 [thread overview]
Message-ID: <87vahabjts.fsf@web.de> (raw)
In-Reply-To: <CAF+kUQW-m2=OPB1Fjf9_r0ftBj5d_c4NSag-r+HfFtkLEvoomw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1140 bytes --]
Hi Alan,
Thank you for your answer!
Alan Manuel Gloria <almkglor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> This is arguably NOT a Guile-specific issue, but rather a general issue.
> Clojure uses its array syntax for parts of its syntax, for example.
>
> The ## seems OK, but how about just plain # ?
That’s part of why it’s Guile specific: I cannot use the plain #,
because that’s the prefix for symbols and illegal syntax for read. I
don’t see a way to do this as simple reader addition.
> So like (using only (read) and not (eval (read))):
>
> ' a b
> => (quote (a b))
> '(a b)
> => (quote (a b))
> # a b
> => #(a b)
> #(a b)
> => #(a b)
I’d like to do it that way, but from what I can tell, doing that would
mean that I have to special-case all special syntax reading, while with
the ## I can harness regular symbol reading in Guile.
The # is the prefix for all kinds of special elements (i.e. #' #, #,@)
and I’m not sure it’s a good idea to take the symbol itself for a given
feature.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 202 bytes --]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
[-- Attachment #3: Type: text/plain, Size: 207 bytes --]
_______________________________________________
Readable-discuss mailing list
Readable-discuss-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/readable-discuss
prev parent reply other threads:[~2017-12-13 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 18:34 wisp literal array syntax for Guile, a good idea? Arne Babenhauserheide
2017-11-12 21:20 ` Matt Wette
[not found] ` <098670CE-873B-4DCC-A111-A88044861BBD-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-12 22:38 ` Arne Babenhauserheide
[not found] ` <87k1yvglih.fsf-S0/GAf8tV78@public.gmane.org>
2017-12-12 22:58 ` Alan Manuel Gloria
[not found] ` <CAF+kUQW-m2=OPB1Fjf9_r0ftBj5d_c4NSag-r+HfFtkLEvoomw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-13 17:29 ` Arne Babenhauserheide [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=87vahabjts.fsf@web.de \
--to=arne_bab-s0/gaf8tv78@public.gmane.org \
--cc=almkglor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=guile-user-mXXj517/zsQ@public.gmane.org \
--cc=matt.wette-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=readable-discuss-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).