# orderedItems[].object.content
If you're at the subscriber (customer) end of the phone line, that's a DAA (Data Access Arrangement), while at the CO (phone company Central Office) side it's a SLIC (Subscriber Line Interface Circuit).
Silicon Labs made chips for both ends, but they may have sold that product line to another vendor. They're commonly used in FXS and FXO cards sold for use with Asterisk PBX software.

# orderedItems[].object.contentMap.fr
If you're at the subscriber (customer) end of the phone line, that's a DAA (Data Access Arrangement), while at the CO (phone company Central Office) side it's a SLIC (Subscriber Line Interface Circuit).
Silicon Labs made chips for both ends, but they may have sold that product line to another vendor. They're commonly used in FXS and FXO cards sold for use with Asterisk PBX software.

# orderedItems[].object.content
I toot therefore I am.

# orderedItems[].object.contentMap.en
I toot therefore I am.

# orderedItems[].object.content
Just finished reading _Agency_ by @GreatDismal, and it was every bit as engaging as _The Peripheral_, which is to say, a LOT. Can't wait to read more.
Also enjoying the TV series very much.

# orderedItems[].object.contentMap.en
Just finished reading _Agency_ by @GreatDismal, and it was every bit as engaging as _The Peripheral_, which is to say, a LOT. Can't wait to read more.
Also enjoying the TV series very much.

# orderedItems[].object.content
I just duplicated one of my threads from the bird here. I'm not sure whether I'll do that in the future.

# orderedItems[].object.contentMap.en
I just duplicated one of my threads from the bird here. I'm not sure whether I'll do that in the future.

# orderedItems[].object.content
This is my first use of std::variant and std::visit. I'm gradually learning more of the C++ standard library.
11/

# orderedItems[].object.contentMap.en
This is my first use of std::variant and std::visit. I'm gradually learning more of the C++ standard library.
11/

# orderedItems[].object.content
I'm using std::variant for an operand, to hold a numeric value, a symbol name (as a string), a PC offset, or nothing (std::monostate). std::variant is like a C union, but type-safe more like an Ada variant record.
10/

# orderedItems[].object.contentMap.en
I'm using std::variant for an operand, to hold a numeric value, a symbol name (as a string), a PC offset, or nothing (std::monostate). std::variant is like a C union, but type-safe more like an Ada variant record.
10/

# orderedItems[].object.content
Anyhow, PEG looks like it can more easily handle Cricket (HP-01) assembly.
9/

# orderedItems[].object.contentMap.en
Anyhow, PEG looks like it can more easily handle Cricket (HP-01) assembly.
9/

# orderedItems[].object.content
PEG parsing also always choose the first match out of any alternatives, so the grammar is never ambiguous and thus there are never shift/reduce conflicts.
A drawback is that grammar rules that work in LALR don't necessarily have the same results in PEG.
8/

# orderedItems[].object.contentMap.en
PEG parsing also always choose the first match out of any alternatives, so the grammar is never ambiguous and thus there are never shift/reduce conflicts.
A drawback is that grammar rules that work in LALR don't necessarily have the same results in PEG.
8/

# orderedItems[].object.content
PEGTL is a C++ header-only library for implementing Parsing Expression Grammar parsers, which usually define lexical and syntactic rules in a single layer.
7/

# orderedItems[].object.contentMap.en
PEGTL is a C++ header-only library for implementing Parsing Expression Grammar parsers, which usually define lexical and syntactic rules in a single layer.
7/

# orderedItems[].object.content
However, the syntax for Cricket (HP-01) assembly makes it more difficult to tokenize with flex, so I'm using C++ with PEGTL this time.
6/

# orderedItems[].object.contentMap.en
However, the syntax for Cricket (HP-01) assembly makes it more difficult to tokenize with flex, so I'm using C++ with PEGTL this time.
6/

# orderedItems[].object.content
I did that before for assemblers for the HP "classic" architecture (e.g. HP-35) and "Woodstock" architecture (e.g. HP-25, HP-67),
using flex and bison
5/

# orderedItems[].object.contentMap.en
I did that before for assemblers for the HP "classic" architecture (e.g. HP-35) and "Woodstock" architecture (e.g. HP-25, HP-67),
using flex and bison
5/

# orderedItems[].object.content
I'm doing free-form rather than column-distinguished, and I'm requiring the label field, if present, to be followed by a comma
4/

# orderedItems[].object.contentMap.en
I'm doing free-form rather than column-distinguished, and I'm requiring the label field, if present, to be followed by a comma
4/

# orderedItems[].object.content
The assembly syntax is ugly because symbols (including labels) can contain almost any character. Instruction mnemonics can contain those, as well as _spaces_.
I think the HP assembler may have split the label, mnemonic, operand, and comment fields based on column positions.
3/

# orderedItems[].object.contentMap.en
The assembly syntax is ugly because symbols (including labels) can contain almost any character. Instruction mnemonics can contain those, as well as _spaces_.
I think the HP assembler may have split the label, mnemonic, operand, and comment fields based on column positions.
3/

# orderedItems[].object.content
I'm not trying to make mine much better, as I just want to assemble the original source code as listed in a patent, which was prototype firmware, and a disassembly of the production firmware.
2/

# orderedItems[].object.contentMap.en
I'm not trying to make mine much better, as I just want to assemble the original source code as listed in a patent, which was prototype firmware, and a disassembly of the production firmware.
2/

# orderedItems[].object.content
I'm writing an assembler in C++ with PEGTL, to assemble HP-01 firmware. The assembler HP used back in the mid-1970s was quite crude. For instance, operands could be numeric literals, symbol names, or PC-relative references (e.g. *+3"), but not general arithmetic expressions.
1/

# orderedItems[].object.contentMap.en
I'm writing an assembler in C++ with PEGTL, to assemble HP-01 firmware. The assembler HP used back in the mid-1970s was quite crude. For instance, operands could be numeric literals, symbol names, or PC-relative references (e.g. *+3"), but not general arithmetic expressions.
1/