JP1 Remotes

I still have some difficulty understanding the key binding and persistence concepts as well as the implementation but wonder what you think of the following: First, a new structure consisting of two elements: one item to hold a data value and another item for a pointer.
Construct a uni-directional ...

Hello again Graham - some more trivial typo feedback:

o "possibly proceded by other bitspecs" - preceded?
o perfomed

other suggestions:

"beyond the pointer position" (two occurrences) - suggest using "above" instead of "beyond" for clarity

for DELETE FROM, an <item>"is deleted" from the stack ...

Yes, I agree with you completely Graham: non-integer durations expressed with decimal points would appear to introduce a needless complication into the protocol and your example illustrates very well how they may be avoided (except perhaps for cases where no common denominator may be found such as ...

A few more questions Graham;

For the statement:
"For a bitspec that translates bits in groups of n, the number of possible combinations is 2 to the power n. The corresponding sequences of bare IRstreams are listed in the order of the bit sequences given by the bitfields"

Should the immediately ...

Yes, I know I didn't get the phrasing or meaning just right - I'm sure you will be able to do much better than my suggestion.

Also, at the risk of splitting hairs I would point out that the document states "The number in a frequency item can include a decimal point. This is the only situation in ...

This is a wonderful document! Thanks for putting it together.

A few typos to be corrected in the next version:

- automated process ro parse
- bit of the unshifed value
- all tbe bits
- bits beyond a cartain point


technical:

These are the only binary forms whose value can be negative

should ...