Micha? Król wrote:
> On 17/05/07, Brian Paul <[EMAIL PROTECTED]> wrote:
>> Ian Romanick wrote:
>>> Is there an easy way in this parser generator to change the grammar for
>>> the TXP instruction? Basically, I want it to be invalid to use TXP with
>>> the SHADOWARRAY2D target.
>> Michael would have to answer that. Michael?
>>
>
> I will look at it tomorrow.
>
>>> Alternately, is there a reason we're using this instead of lex & yacc?
>> I think Michael just used what was familiar to him.
>>
>>
>>> I used lex & yacc to write a unified parser for another project that
>>> handles ARB_{vertex,fragment}_program (up to vp3 and fp2), the various
>>> NV vertex and fragment programs, and ATI_text_fragment_shader. I could
>>> probably adapt it to work with Mesa without too much trouble.
>>>
>>> Opinions?
>> I guess I'd prefer using standard tools like lexx and yacc. Though, I'd
>> do research to see if there's anything newer/nicer nowadays.
>>
>
> If my memory serves me right, there was at least one attempt in the
> past to kill off those syn files, but they are still alive to this
> day.
>
> Ian, if this is no problem for you, feel free to replace it with yacc
> grammars, just please keep the old ones #ifdefed for a while, if
> possible. The reason I used custom grammar in the first place was that
> I wasn't aware of any (not only open source) compiler-compiler (lack
> of Internet!) so I just invented one.
>
I think the Zack/Roberto LLVM tree has done just this. Unfortunately
for this immediate problem, they target a whole new intermediate
representation.
Keith
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
