Jan Nieuwenhuizen skribis:
> Not yet, three patches I sent are pending, waiting for my copyright
> assignment to get through, I think.
Well, we received it just now. :-)
Ludo’.
Jan Nieuwenhuizen skribis:
> Not yet, three patches I sent are pending, waiting for my copyright
> assignment to get through, I think.
Indeed, you’re not listed yet. If it’s been more than 3 weeks or so,
don’t hesitate to ping them by email.
Ludo’.
Oh, it took me more than a month for shipping the assignment paper
years before. ;-)
Anyway, it's fine for me, because you choose to implement it with
source-property which prevent me to modify the whole structure of
parsing tree and test cases. So I don't have to wait for the patch,
it's cool for
Nala Ginrut writes:
> I wonder if Guile master has updated to the latest lalr-scm, since I
> can't see the expected result.
> If the answer is no, I have to request for it, it's important for our
> multi-lang hacking.
Not yet, three patches I sent are pending, waiting for my copyright
assignment
Thanks for reply!
I wonder if Guile master has updated to the latest lalr-scm, since I
can't see the expected result.
If the answer is no, I have to request for it, it's important for our
multi-lang hacking.
Thanks!
On Mon, Oct 27, 2014 at 4:11 AM, Jan Nieuwenhuizen wrote:
> Hi,
>
> Saw your que
Hi,
Saw your question on irc.
Attached is a modification on your `simple' language that demonstrates
transparent source locations.
The explicit, Bison-like locations work just like they do in Bison...eg
something like:
;; helper
(define (note-location ast loc)
(when (supports-sour
