Re: FW: which parser to use

[David Durham]

   There is a 'bison.simple' file that gets pasted in at the top of the
bison output file.... I believe you should be able to use a modified
version of  this file by supplying any needed functionality yourself
instead of using glibc...   I can't remember at the moment, but I think
there's as environment variable ($BISON_SIMPLE) that bison will use to
get where the path/file of bison.simple is, so point bison to your
modified version...

(Also, there's a alternate bison.hairy file that bison will use, but I'm
not sure under what circumstances that it uses that file)

-- Davy

On Fri, 2001-10-26 at 15:36, MEHTA,HIREN (A-SanJose,ex1) wrote:
> Hi List,
> 
> I want to generate a parser from a grammer which can be used
> inside a kernel. The problem with bison/yacc is that it includes
> stdlib.h and it uses malloc/realloc and other routines. Is there
> any way to get around this ? Or should I be using some other
> parser generator instead of yacc/bison ? I have the same problem
> with lex which includes stdio.h  and other header files which
> are useless for kernel. 
> 
> Please advise on how I should go about generating parser which 
> is going to be part of kernel.
> 
> Please cc me as I am not subscribed to the list.
> 
> TIA.
> Regards,
> -hiren
> 
> _______________________________________________
> Help-bison mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/help-bison