unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: tomas@fabula.de
Cc: Neil Jerram <neil@ossau.uklinux.net>, guile-devel@gnu.org
Subject: Re: Adding stuff to the core distro (was Re: Infix syntax)
Date: Sat, 19 Oct 2002 06:50:56 +0200	[thread overview]
Message-ID: <20021019045056.GB22744@www> (raw)
In-Reply-To: <m0d6qadq3w.fsf@hobitin.ucw.cz>

On Wed, Oct 16, 2002 at 11:35:15PM +0200, Daniel Skarda wrote:
> 

[Neil: macro instead of read-hash-extension]

>   Wow, that's clever. It seems I played with read hash extension too much that I
> have not noticed simpler (and schemish) way... (On the other hand, #[] is shorter :-)

Isn't Scheme surprising to us mortals ;-)

[...]

>   No other tricky whitespace handling is performed (it would be dangerous, since
> #\- and #\* are often used in scheme symbols).

Albeit dangerous, I'd vote for having it (as an option, at least). It should just
accept ``classical'' identifiers (C-like if you wish). Background: I'm playing with
the idea of letting users enter formulas for a small application (users not aware
of Scheme), and I think the ``classical'' syntax is easier to grasp for them.

>   infix.scm proposal, second edition:
>  ------------------------------------- 

[snip]

Yes, makes sense to let the macro expander do the parse work. Maybe a
first-stage tokenizer for the ``micro-syntax'' (this would be called
a lexer in a more traditional framework?) could be thrown in as an
option.

Thanks
-- tomas


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-10-19  4:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 11:26 Infix syntax Daniel Skarda
2002-10-05  8:55 ` Neil Jerram
2002-10-06  8:05   ` Daniel Skarda
2002-10-08 21:51     ` Adding stuff to the core distro (was Re: Infix syntax) Neil Jerram
2002-10-08 22:40       ` Han-Wen Nienhuys
2002-10-09  3:30       ` Rob Browning
2002-10-09 18:15         ` Neil Jerram
2002-10-09 20:17           ` Rob Browning
2002-10-10 12:20             ` Daniel Skarda
2002-10-10 12:29       ` Daniel Skarda
2002-10-13 14:28         ` Neil Jerram
2002-10-16 21:35           ` Daniel Skarda
2002-10-19  4:50             ` tomas [this message]
2002-10-20 19:15               ` Daniel Skarda
2002-10-21  9:36                 ` tomas
2002-10-21 18:21                 ` Neil Jerram
2002-10-19 22:17             ` Christopher Cramer
2002-10-20 19:05               ` Daniel Skarda
2002-10-10 16:06       ` Daniel Skarda
2002-10-10 17:12         ` Rob Browning
2002-10-10 18:46           ` Clinton Ebadi
2002-10-10 22:24           ` Lynn Winebarger
2002-10-13 15:09           ` Proposal for scope of core distro Neil Jerram
2002-10-17  0:10           ` Adding stuff to the core distro (was Re: Infix syntax) Daniel Skarda
2002-10-18  7:24             ` Lynn Winebarger
2002-10-20 20:25               ` Daniel Skarda
2002-10-10 18:08         ` Bill Gribble
2002-10-17  2:42           ` Daniel Skarda
2002-10-13 14:27         ` Neil Jerram
2002-10-17  1:25           ` Daniel Skarda
2002-10-19 10:56             ` Neil Jerram

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=20021019045056.GB22744@www \
    --to=tomas@fabula.de \
    --cc=guile-devel@gnu.org \
    --cc=neil@ossau.uklinux.net \
    /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).