public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Damien.MATTEI@univ-cotedazur.fr, kawa@sourceware.org
Subject: Re: A bug in Kawa reader
Date: Fri, 3 Mar 2023 09:05:14 -0800	[thread overview]
Message-ID: <c69f6d8e-cf68-ab81-bd2c-7c5dbe2f5ae3@bothner.com> (raw)
In-Reply-To: <dc72bd1c-5f51-8a85-71d4-adfc071846ad@oca.eu>

On 3/2/23 23:08, Damien Mattei wrote:
> noone interested in making a reader that support SRFI-105 ,curly infix for Kawa? it should be quite easy, when i have time i prospect to do it...

I see little value in srfi-105.  Who would use it and why?

If you want infix notation with Scheme semantics, you
might find my "KaShell" experiment interesting:
     http://kashell.org/
(KaShell was previously called "q2".)
There are some examples/tests in gnu/q2/testsuite in the source-code.

KaShell has infix operators, with precedence - without reserved operators.
(While not implemented, a 'define-operator' would be conceptually
similar to define-syntax, but with precedence levels.)

On goal of KaShell is to be a nice language for REPL, specifially
like a "rich shell" with typed values.  That is why it avoids
needless parenteses and semi-colon-like delimiters.
Instead, KsShell uses indentation.

Large parts of the syntax I haven't decided on yet.  You can "fall back"
on using Scheme macros:
     let ((x (3 * 4))) (x + 20)
which is equivalent to Scheme:
     (let ((x (* 3 4))) (+ x 20))
but of course that is not very satisfactory.

I haven't worked on KaShell in almost 5 years, but hopefully I'll
get back to it someday.  Until then, maybe someone will be inspired.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2023-03-03 17:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 22:14 Panicz Maciej Godek
2023-03-02 22:30 ` Per Bothner
2023-03-03  7:08   ` Damien Mattei
2023-03-03 17:05     ` Per Bothner [this message]
2023-09-18  5:09       ` Damien Mattei
2023-03-03  7:45   ` Panicz Maciej Godek
2023-03-03  8:17     ` Sudarshan S Chawathe
2023-03-03  8:29       ` Panicz Maciej Godek
2023-03-03 10:19     ` Lassi Kortela

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c69f6d8e-cf68-ab81-bd2c-7c5dbe2f5ae3@bothner.com \
    --to=per@bothner.com \
    --cc=Damien.MATTEI@univ-cotedazur.fr \
    --cc=kawa@sourceware.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).