On Jun 26, 2015, at 1:43 PM, Matt Wette wrote:
> On Jun 3, 2015, at 8:40 PM, Matt Wette wrote:
>> My current project is a lalr module.
>
> Here is a slight update on my parser generator.
> 1) I have added a "hashify" procedure that allows one to set up the parser
> and lex'er to use integers
On Jun 3, 2015, at 8:40 PM, Matt Wette wrote:
> My current project is a lalr module.
Here is a slight update on my parser generator.
1) I have added a "hashify" procedure that allows one to set up the parser and
lex'er to use integers instead of symbols.
2) I have updated the specification par
On Sat, 2015-06-06 at 10:19 -0700, Matt Wette wrote:
> On Jun 4, 2015, at 1:41 AM, Nala Ginrut wrote:
> >
> >> 1) There is no specification of terminals. Terminals are detected in
> >> rules (via fenders) as quoted symbols or characters.
> >>Example of terminals: 'number, #\+
> >
> > hmm..
On Jun 4, 2015, at 1:41 AM, Nala Ginrut wrote:
>
>> 1) There is no specification of terminals. Terminals are detected in
>> rules (via fenders) as quoted symbols or characters.
>>Example of terminals: 'number, #\+
>
> hmm...and strings? Do you have plan to let users choose whether to use
On Wed, 2015-06-03 at 20:40 -0700, Matt Wette wrote:
> (Accidentally sent to guile-devel.)
>
> Having fun with all the great code, and documentation, in guile 2.
>
> My current project is a lalr module. Last December I wanted to start
> working on an interpreter for modelica in guile. Guile has
(Accidentally sent to guile-devel.)
Having fun with all the great code, and documentation, in guile 2.
My current project is a lalr module. Last December I wanted to start working on
an interpreter for modelica in guile. Guile has a lalr parser generator
(system base lalr). When I started l