Lex / Yacc problem

[Xose Lois Castro]

Hi, mates:

I'm trying to write a grammar to read files with the following structure,
for example:
text
...
more text

'text' ='another text',

...

'more text' = 'some more text',

text
...

Text can contain any kind of characters and symbols: a-z, 0-9, ?, *, ], (, {...

When applying this file to the parser, I only want things in the right
side of the "=>" to be in the output.

I paste here some parts of my grammar:

lex)

[\n] { return 0; }
' { return SYMBOL; }
= { return ARROW; }
, { return COMMA; }
" "+ { return SPACE; }
.+ { yylval = strdup(yytext); return TEXT; }

yacc)

line: SYMBOL TEXT SYMBOL SPACE ARROW SPACE SYMBOL TEXT SYMBOL COMMA
{ printf("%s\n", $8); }
;
With YYSTYPE defined as "char *"

My code compiles perfectly but when I run it I get a lot of syntax errors,
and nothing is in the output.

I'd be very pleased if somebody gives my some advice in how to build a
correct grammar for my purpose.
Best regards

--

Xose Lois

[dj3vande]

In article <pa************ *************** *@yahoo.com>,
Xose Lois Castro <gt************ *****@yahoo.com wrote:

[Subject line: "Lex/Yacc problem"]

>My code compiles perfectly but when I run it I get a lot of syntax errors,
and nothing is in the output.

I'd be very pleased if somebody gives my some advice in how to build a
correct grammar for my purpose.

Code generators like lex and yacc are not defined by the C language and
are therefore beyond the scope of comp.lang.c.

comp.compilers might be a better place to ask.
dave

--
Dave Vandervies dj3vande at eskimo dot com

Yes, P.J. Plauger is more or less a regular.

Less, I think. More of a sporadic than a regular.
--Keith Thompson and Richard Heathfield in comp.lang.c

[Flash Gordon]

Xose Lois Castro wrote, On 10/01/08 22:25:

Hi, mates:

As far as I am aware you are not my mate.

<snip>

I paste here some parts of my grammar:

lex)

<snip>

yacc)

<snip>

I see no C, only lex and yacc neither of which are C. I suggest you find
a group or mailing list where they are topical. It might be worth
checking out comp.compilers, but check there FAQ and at least a weeks
worth of posts before posting there. Alternatively comp.programmin g,
comp.unix.progr ammer or comp.lang.misc might be worth a try.
--
Flash Gordon