From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailtransmit05.runbox.com (mailtransmit05.runbox.com [IPv6:2a0c:5a00:149::26]) by sourceware.org (Postfix) with ESMTPS id 24F183858439 for ; Fri, 3 Mar 2023 17:05:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 24F183858439 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=bothner.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=bothner.com Received: from mailtransmit03.runbox ([10.9.9.163] helo=aibo.runbox.com) by mailtransmit05.runbox.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1pY8qZ-003bpq-9g; Fri, 03 Mar 2023 18:05:31 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bothner.com ; s=selector1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:To:Subject:MIME-Version:Date:Message-ID; bh=F5ChW/w2+iXtnKpuaT995/YG3zRNzJ3pp0bNuungI+w=; b=iu2PxUq/9UccsjmGzUTfkKzP0e REwOdU19cxWuveM0gr7uzjwgo+ORYUwZUtj8oKLjjJwdLTTmt0mCyYXAEWBOOr2itkLoXcGExA05k ERAV62fngVGhF3Vofv0uOgjnGOvegsRy4hDfTgb0X/YL4JQQf2iAbf6JgIKSwvo0iB0Bak9SViuAR M8YkhgmAopLbg2lopebtzWLKlQAMmgBzustqJ7J/etKoBHSa6NnxF1gvvDZmC7ELxEJcR99MRfZwQ ZGhM5RMyKVLX9uI7cZJYSnQuHqxZdYhHNCjHVFJA0g+XpeJWBuc4nGpndS6LuPJS1oUBGU+pk930r F8fk/owA==; Received: from [10.9.9.72] (helo=submission01.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1pY8qY-0006dN-Hf; Fri, 03 Mar 2023 18:05:30 +0100 Received: by submission01.runbox with esmtpsa [Authenticated ID (524175)] (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) id 1pY8qO-0005Mb-56; Fri, 03 Mar 2023 18:05:20 +0100 Message-ID: Date: Fri, 3 Mar 2023 09:05:14 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: A bug in Kawa reader Content-Language: en-US To: Damien.MATTEI@univ-cotedazur.fr, kawa@sourceware.org References: <1dccac2d-bf49-9326-446d-6b00d77595a3@bothner.com> From: Per Bothner In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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/