On Nov 10, 2007 1:43 PM, Marco Gerards <[EMAIL PROTECTED]> wrote:
> Bean <[EMAIL PROTECTED]> writes:
>
> >> In the tarball?
> >
> > Yes.
>
> Could you send the files to the list as attachments? Or whatever is
> relevant. tarballs on a mailinglist are very inconvenient. :-/
>
> --
> Marco
>
>
>
>
Bean <[EMAIL PROTECTED]> writes:
>> In the tarball?
>
> Yes.
Could you send the files to the list as attachments? Or whatever is
relevant. tarballs on a mailinglist are very inconvenient. :-/
--
Marco
___
Grub-devel mailing list
Grub-devel@gnu.or
On Sun, Jul 22, 2007 at 06:21:18PM +0200, Marco Gerards wrote:
> The code already uses an AST. Or what do you mean?
I mean the test program.
> If I am not mistaken, you are going over parser.y to make it work with
> more situations and to introduce proper error handling. Or am I
> mistaken?
Th
Bean <[EMAIL PROTECTED]> writes:
> On Sun, Jul 22, 2007 at 03:06:49PM +0200, Marco Gerards wrote:
>> You are right that it has advantages. But I prefer using an Abstract
>> Syntax Tree. It is used a lot in most literature on parsers, clean
>> and easy to understand.
>>
>> The disadvantage is th
On Sun, Jul 22, 2007 at 03:06:49PM +0200, Marco Gerards wrote:
> You are right that it has advantages. But I prefer using an Abstract
> Syntax Tree. It is used a lot in most literature on parsers, clean
> and easy to understand.
>
> The disadvantage is that you need a separate free routine for e
Bean <[EMAIL PROTECTED]> writes:
Hi Bean,
> I have written a small problem to test my parse.y, to compile, use the
> following commands:
>
> bison -d -p grub_script_yy -b grub_script parser.y
> gcc -oparser parser.c lexer.c grub_script.tab.c
>
> After compilation, run parser
>
> ./parser
>
> Ju
I forget to include the attachment. Here is it.
--
Bean
parser.tar.gz
Description: Binary data
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
Hi,
I have written a small problem to test my parse.y, to compile, use the
following commands:
bison -d -p grub_script_yy -b grub_script parser.y
gcc -oparser parser.c lexer.c grub_script.tab.c
After compilation, run parser
./parser
Just enter the commands after '##', and the syntax tree asso