unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: Panicz Maciej Godek <godek.maciek@gmail.com>
Cc: Mark H Weaver <mhw@netris.org>, Guile Devel <guile-devel@gnu.org>
Subject: Re: Wisp as shipped language in Guile?
Date: Sat, 13 May 2017 11:44:08 +0200	[thread overview]
Message-ID: <87inl53xm8.fsf@web.de> (raw)
In-Reply-To: <CAMFYt2ZVd6Q+UFUhrcSOwxfo2gYfmUP33vqisL8_x+z8MpwETA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2268 bytes --]


Panicz Maciej Godek <godek.maciek@gmail.com> writes:

> 2017-05-13 3:52 GMT+02:00 Mark H Weaver <mhw@netris.org>:
>
>> Hi Arne,
>>
>> Arne Babenhauserheide <arne_bab@web.de> writes:
>> > A few weeks ago I asked in IRC whether wisp[1] could be included with
>> > Guile in modules/language/wisp to allow every guile users to run wisp
>> > code from any Guile installation via
>> >
>> >
>> >     $ guile --language=wisp [<file>]
>> >
>> >
>> > Essentially this is about making wisp as language part of the
>> > "batteries" of Guile.
>>
>> About 4.5 years ago, I went out on a limb and added SRFI-105 (curly
>> infix expressions) to core Guile.  Even now, I'm of the opinion that
>> judicious use of curly infix could be beneficial for readability, but as
>> far as I can tell, there's been essentially no uptake.  If I'm wrong
>> about that, please let me know.

I’m using curly infix in cond-expressions, both with wisp and with
regular Scheme:

(cond
  ({a < 5}
   (something)
   (more))
  ({a > 7}
   (something-else)))

cond
  : {a < 5}
    something
    more
  : {a > 7}
    something-else


>> Although (a subset of) SRFI-105 seems like a clear win to me, I cannot
>> say the same of either Wisp or SRFI-110 (Sweet expressions).
>>
> "The idea of introducing Algol-like syntax into Lisp keeps popping up and
> has seldom failed to create enormous controversy between those who find the
> universal use of S-expressions a technical advantage
…

This is a nice read, but does not apply to Wisp itself, since Wisp just
infers the parentheses from indentation but otherwise does not change
anything.

It does apply to some degree to SRFI-105, but not fully.
A rationale is provided here:
https://web.archive.org/web/20160505180131/http://srfi.schemers.org/srfi-105/srfi-105.html#rationale_changereader

(being able to use infix for pattern matching)

That said: I like is as infix very much and would love to see it
included — e.g. in (ice-9 is).

On the other hand, a SRFI for is would make it easier to build
cross-system scheme with it.

> and (is x < y <= z) is more concise than (and (< x y) (<= y z)).

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-05-13  9:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-07 20:56 Wisp as shipped language in Guile? Arne Babenhauserheide
2017-05-08  2:34 ` Christopher Allan Webber
2017-05-13  1:52 ` Mark H Weaver
2017-05-13  7:24   ` Panicz Maciej Godek
2017-05-13  9:44     ` Arne Babenhauserheide [this message]
2017-05-16 19:27       ` nice option to have Fox
2017-05-18 23:03   ` Wisp as shipped language in Guile? Arne Babenhauserheide
2017-05-19 14:54     ` Wisp for Racket / Dr.Racket ? Fox
2017-05-19 21:06     ` more extensible reader directive, was: Wisp as shipped language in Guile? Arne Babenhauserheide
2017-08-11  9:04     ` Arne Babenhauserheide
2017-08-11 17:28       ` Nala Ginrut
2017-09-17 19:10         ` Arne Babenhauserheide
2017-09-17 20:28           ` Matt Wette
2017-09-17 23:22             ` Arne Babenhauserheide
2017-09-18  0:24               ` Matt Wette
2017-09-18 19:21                 ` Arne Babenhauserheide
2017-09-19 14:10                 ` Christopher Allan Webber
2017-09-19 23:46                   ` Nala Ginrut

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=87inl53xm8.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=godek.maciek@gmail.com \
    --cc=guile-devel@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).