unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Damien Mattei <damien.mattei@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Python slices in Scheme
Date: Wed, 21 Jun 2023 09:45:19 +0200	[thread overview]
Message-ID: <CADEOadd2U62qyw=iLPbgoYh6CJg-qZ3vHbHS+1yE=aSAV0zDQQ@mail.gmail.com> (raw)
In-Reply-To: <cd846f57-1d97-444c-8963-7fcf352d1778@robbyzambito.me>

what troubled me is the uppercase in Front and the sense and i'm not easy
with english as being french. Sexp i already know as symbolic expressions ,
that are in Scheme prefix expression but could also be infix or postfix,
SRFI 105 being an infix reader for Scheme noted with curly syntax but they
exist only at the reader stage before evaluation, only Scheme prefix
expression are evaluated being converted from infix to prefix, it can be
easily put in evidence when quoting an expression and displaying it as in
this example:
;; Racket example
'{#(1 2 3 4 5 6 7 8 9)[2 / 5 / 1]}
'($bracket-apply$ #(1 2 3 4 5 6 7 8 9) 2 / 5 / 1)

;; Guile example
scheme@(guile-user)> '{"0123456789"[5 / 2 / -1]}
$2 = ($bracket-apply$ "0123456789" 5 / 2 / -1)

note that in racket my SRFI 105 reader adaptation display the result quoted
too:'($bracket-apply$ #(1 2 3 4 5 6 7 8 9) 2 / 5 / 1)
but not of this happen in Guile, i really do not know what should be the
good result in Scheme,anyway it i think it is only a representation, it
does not change the computation when used in a program.
Damien


On Tue, Jun 20, 2023 at 1:23 PM Robby Zambito <contact@robbyzambito.me>
wrote:

> Jun 20, 2023 02:42:34 Damien Mattei <damien.mattei@gmail.com>:
>
> > what is Sexp Front?
>
> On X front is an idiom - search for "on that front" if you want to see
> examples.
>
> Sexp refers to symbolic expressions, which is the typical syntax of Lisp.
>
> Robby
>


  reply	other threads:[~2023-06-21  7:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-18 16:58 Python slices in Scheme Damien Mattei
2023-06-18 18:51 ` Dr. Arne Babenhauserheide
2023-06-18 20:20   ` Damien Mattei
2023-06-18 21:44     ` Dr. Arne Babenhauserheide
2023-06-19  1:52 ` Jay Sulzberger
2023-06-19 16:36   ` lloda
2023-06-19 19:44     ` Zelphir Kaltstahl
2023-06-20  6:39     ` Damien Mattei
2023-06-23 13:26     ` Jay Sulzberger
2023-06-23 19:14     ` Damien Mattei
2023-06-20  6:41   ` Damien Mattei
2023-06-20 11:22     ` Robby Zambito
2023-06-21  7:45       ` Damien Mattei [this message]
2023-06-23 13:17 ` Jay Sulzberger
2023-06-24 13:08   ` Damien Mattei
2023-06-24 16:18     ` Dr. Arne Babenhauserheide
2023-06-24 20:24       ` Damien Mattei

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='CADEOadd2U62qyw=iLPbgoYh6CJg-qZ3vHbHS+1yE=aSAV0zDQQ@mail.gmail.com' \
    --to=damien.mattei@gmail.com \
    --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).