unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: 康桥 <usakq12345@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Anyone who had read the src of lalr-scm?
Date: Tue, 02 Sep 2014 08:07:43 +0200	[thread overview]
Message-ID: <87d2beimhc.fsf@zigzag.favinet> (raw)
In-Reply-To: <39x8o2nv9t0tyr0uxk3x44r0.1386325408787@email.android.com> ("康桥 "'s message of "Fri, 06 Dec 2013 18:30:16 +0800")

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

() 康桥 <usakq12345@gmail.com>
() Fri, 06 Dec 2013 18:30:16 +0800

   But I still leave one function not understand.  It's function
   digraph in the macro lalr-parser in file lalr.scm.  It seems
   that this function is trying to traverse a digraph and make
   each FOLLOW set corresponding a vertex in the digraph the union
   of it and the FOLLOW sets corrsponding the vertices which can
   be reached from the vectex I mentioned before.  But I can't
   figure out what algorithm it uses.

   Anyone who know this algorithm?

At first glance it seems to be a standard fanout computation.
What do you mean by "know"?  Are you looking for its name?

   BTW, should we rewrite lalr-scm in a more scheme way(even to
   make the process of parser generating slower)?

Why don't you go ahead and try, then post your findings?

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2014-09-02  6:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 10:30 Anyone who had read the src of lalr-scm? 康桥
2014-09-02  6:07 ` Thien-Thi Nguyen [this message]

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=87d2beimhc.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=usakq12345@gmail.com \
    /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).