From: Daniel Skarda <0rfelyus@ucw.cz>
Cc: guile-devel@gnu.org
Subject: Re: Adding stuff to the core distro (was Re: Infix syntax)
Date: 20 Oct 2002 21:05:10 +0200 [thread overview]
Message-ID: <m0smz1c4nt.fsf@hobitin.ucw.cz> (raw)
In-Reply-To: <20021019171721.A18616@kiwi.pyrotechnics.com>
> On Wed, Oct 16, 2002 at 11:35:15PM +0200, Daniel Skarda wrote:
> > ps: Sometimes I also use read-hash extension for shorter
> > (sed|awk|perl|...)-like regular expressions: #/foo.*bar/i, sometimes
> > I also use srfi-10 #,(rx "foo.*bar" icase). Do you think that other
> > guilers would benefit from such hairy extensions?
>
> Ack. I actually started using #/ for SQL.
Oops :-) How do you use it for SQL?
I usually do not support adding new syntactic sugar to Scheme, but
sometimes I simply can not resist :-)
I picked up #/regexp/ since almost all programmers are familiar with
similar syntax from perl, awk, sed and other shell utils.
The advantage of this style of writing regexps is its "regexpness" :-)
and the ability to create regexp during read (no need to "toplevel" define
etc). The later can also be achieved by #,(rx "regexp"), which is more
schemish but less regexpish, it is longer and you have to write two escapes
instead of one (definitely not tempting features for lazy programmers :-).
As I wrote in another email I would like to add lisp-like readtables to
Guile read so it would be possible to make read-hash-extension per-module.
IMHO Guile should come with modules that implement/activate syntax
extensions (like infix syntax, #/regexps/, #,(rx "regexp") or whatever),
if we preserve following rules:
1) extensions are off by default
2) no Guile code (srfi,ice-9) use or depends on these extensions.
3) user is clearly warned that these extensions are not portable
4) one extensions does not clash with another...
Maybe we also should pick some policy to prevent future clashes
(#/regexps/ versus your #/ in SQL)
0.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-10-20 19:05 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
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 [this message]
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=m0smz1c4nt.fsf@hobitin.ucw.cz \
--to=0rfelyus@ucw.cz \
--cc=guile-devel@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).