

In IrScrutinizer, the word "generate" is used instead of "render". There are also a few extensions to the IRP notation as described in the official documentation. With the exception of these restriction, the implementations should be complete, down to specification holes. (This is inherited from the use of Java's long type. One infinite repeat is not known to me.) Also, individual bitfields are restricted to 63 bits of length or less. (A realistic protocol, or use case, requiring more than In the present implementation, only one infinite repeat is allowed. With numerical values assigned to the parameters. It is probably to be implemented as a traversing of the parse tree of an IRP protocol, There are a number of interesting use cases for a nice parser/tree traverser: Rendering The reason for this project is not (just) to migrate IrpMaster to ANTLR4 - version 3 is still operational,Īnd no more broken than it was at the start. Generate code from the IRP form is a natural wish.

Although DecodeIR and IrpMaster (through the data base IrpProtocols.ini)Īgree on most (but not all) protocols, this consists of two different, dis-coupled sources of protocol information. Unfortunately, this means that using version 4 instead of version 3 is not like updating a compiler or such,īut "necessitates" a complete rewrite of the actions.īut that is of course not all: Both DecodeIR by John Fine and the Analyzer by Graham Dixon have shown to beĮssentially impossible to maintain and extend. In IrpMaster (like the "ugliness" of embedding actions within the grammar, no left recursion, and much more). The "new version"ĪNTLR4 is really not a new version, but a completely different tool, fixing most of the quirks that were irritating The Irp parser therein is based upon a ANTLR3 grammar. This program can be considered as a successor of IrpMaster. This work surely would not exist without the JP1 forum. (in particular with Dave Reed ("3FG") and Graham Dixon ("mathdon")). (in particular of course DecodeIR, and the discussions

I would like to acknowledge the influence of the JP1 forum, both the programs The project consists of an API library that is also callable from the command line as a command line program.Ī GUI is possible, as well as the integration in GUI programs, like IrScrutinizer. This is a new program, written from scratch, that is intended to replace IrpMaster, DecodeIR, and (most of) ExchangeIR,Īnd much more like potentially replacing "all" hand written decoders/renderers. Parser for IRP notation protocols, with rendering, code generation, recognition applications.
