>
> Maybe the parser/lexical analyzer should emit tokens for the EEPROM.
>
> Best regards,
>
> Spehro Pefhany --"it's the network..."            "The
> Journey is the reward"
> speff@interlog.com             Info for manufacturers:

Or, generate C/assembly code that will evaluate the conditions and
activate the actions. One good side of this approach is that you can
have the power of C in your rule language without having to develop
much.

Tal

> -----Original Message-----
> From: pic microcontroller discussion list
> [mailto:PICLIST@MITVMA.MIT.EDU] On Behalf Of Spehro Pefhany
> Sent: Wednesday, May 28, 2003 4:45 PM
> To: PICLIST@MITVMA.MIT.EDU
> Subject: Re: [PIC]: Parser
>
>
> At 03:55 PM 5/28/2003 -0700, you wrote:
> >Carlos, what are the requirements from your systems, are the rules
> >static and set once or are they dynamic and can change at runtime ?
> >
> >If they are static, you want to do as much as possible off line and
> >only save a compiled version of the rules conditions and
> actions. This
> >can be represented as data (using the proper interpreter) or as code
> >(more efficient and probably simpler). In both cases, you
> can generate
> >them by hand or using some compiler for a rule language you
> can define
> >(and implement using Lex, Yacc, JavaCC etc).
>
> Maybe the parser/lexical analyzer should emit tokens for the EEPROM.
>
> Best regards,
>
> Spehro Pefhany --"it's the network..."            "The
> Journey is the reward"
> speff@interlog.com             Info for manufacturers:
http://www.trexon.com
Embedded software/hardware/analog  Info for designers:
http://www.speff.com

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics