unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Stefan Israelsson Tampe <stefan.tampe@spray.se>
To: guile-devel@gnu.org
Subject: Re: FOL
Date: Thu, 16 Sep 2010 23:02:30 +0200	[thread overview]
Message-ID: <201009162302.30541.stefan.tampe@spray.se> (raw)
In-Reply-To: <87mxrhjucd.fsf@gnu.org>

> 
> What are your plans for your Prolog compiler, in terms of releases,
> merges, and whatnot?  :-)

This is on my list before I think that it will be merged/released a beta
1.
I'm in the process to replace the matchers with modified Shinn. The main
problem using prompts is that I don't get tail call's, I do have it with 
the fragile umatch and Shinn! Also I will not need to patch guile sources.
I'll use a pure Scheme backend and a c-code version.

2. Write test test code - which now is a good time to start when there are
decent syntax error reports.


> > For setting up the error reporting I used a pdf
> > describing the syntax-parse macro
> > 
> >   http://www.ccs.neu.edu/scheme/pubs/icfp10-cf.pdf
> 
> Yeah, that seems like an improvement in terms of error detection and
> error reporting (better than “source expression failed to match any
> pattern”...).
> 
> However, I don’t like the aesthetics: keywords, and, worse, type
> annotations embedded in identifiers.

The syntax can be fixed, any ideas?

/Stefan



  reply	other threads:[~2010-09-16 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 19:00 FOL Stefan Israelsson Tampe
2010-09-16 19:39 ` FOL Andy Wingo
2010-09-16 20:40 ` FOL Ludovic Courtès
2010-09-16 21:02   ` Stefan Israelsson Tampe [this message]
2010-09-16 21:09     ` FOL Ludovic Courtès

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=201009162302.30541.stefan.tampe@spray.se \
    --to=stefan.tampe@spray.se \
    --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).