[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Hi everyone,
From: |
Akim Demaille |
Subject: |
Re: Hi everyone, |
Date: |
Sun, 17 Feb 2019 15:53:20 +0100 |
>> Le 17 févr. 2019 à 14:17, address@hidden <address@hidden> a écrit :
>>
>> Is there a way i can put my c source code not inside one the the lexer.l or
>> parser.y files ? so i can keep tem separate from the rules ?
Two opposite answers:
I said:
> Le 17 févr. 2019 à 15:49, Akim Demaille <address@hidden> a écrit :
>
> No, sorry. There are several approaches to parsing, one which is fully
> declarative and your rules are "pure". That's not the case of Flex/Bison:
> you must define rules with actions. Yet you should keep your action simple
> and move complex processing into functions.
Uxio said:
> Le 17 févr. 2019 à 15:46, Uxio Prego <address@hidden> a écrit :
>
> Yes of course, by inclusion of headers, in a very much
> common way. You can then manipulate shorter *.y and
> *.l docs, but this is not going to fix any Bison usage issue
> you are having.
And of course Uxio is right. You can put the function you depend upon in other
compilation units (i.e., other *.c files). What I meant is: Flex and Bison are
useless if you don't *call* code from your actions.
- Hi everyone,, address@hidden, 2019/02/17
- Re: Hi everyone,, address@hidden, 2019/02/17
- Re: Hi everyone,, address@hidden, 2019/02/17
- Re: Hi everyone,, Uxio Prego, 2019/02/17
- Re: Hi everyone,, address@hidden, 2019/02/17
- Re: Hi everyone,, address@hidden, 2019/02/17
- Re: Hi everyone,, address@hidden, 2019/02/17
- Re: Hi everyone,, Uxio Prego, 2019/02/17
- Re: Hi everyone,, Akim Demaille, 2019/02/17
- Re: Hi everyone,,
Akim Demaille <=
- Re: Hi everyone,, address@hidden, 2019/02/17
- Re: Hi everyone,, Uxio Prego, 2019/02/17
- Re: Hi everyone,, address@hidden, 2019/02/17
- RE: Hi everyone,, Jannick, 2019/02/17