redcmd / qcpu-syntax-highlighter Goto Github PK

The QCPU CLI implements an optional closure to specify the override address / new pointer location.

A label can be defined like .label(anybaseint):, with anybaseint being something like:

• 0b00001010 (binary, any bitcount is possible)
• 0x0A (hexadecimal)
• 10 (decimal)

It's optional, so .label: is still possible (but not empty: .label():)

The QCPU CLI allows the programmer to separate instructions by commas, and this is mostly used for second-byte instructions like IMM, JMP and memory operations. In the highlighter, these commas are marked as invalid, they're red.

For example, an instruction might be IMM 1, 0x05 or MST 0, 0xEA, and with macros: IMM @loc, @word.

The parser of QCPU CLI doesn't mind having things like INC 0, INC 0, INC 0, but practically, the programmer should never do that.

Spaces are not permitted in $string notations, whilst QCPU CLI parses it correctly.

If I insert a label as a separate line and press enter, an indentation is automatically formed, while it's not suffixed by : (because it's not a label definition, rather using an existing label). It does not happen when I put the label on the same line like CPS, with a comma separating them, such as CPS, .@return_label. See the video for reference:

For a future version, tooltips whenever using headers or declarations would be neat. If you were to create a header, like:

@HEADER MEMORYITERATOR memory_pointer_label closure_label

Upon using it, @MEMORYITERATOR, just having those two arguments (memory_pointer_label and closure_label) are a good reference for ease-of-programming. Besides, it'd be helpful to have a list of declarations (which are only in that file, not across-files like headers) when you type @.

Mostly for immediate bytes, integers can be negative as well as positive. However, the numeric parser doesn't include that as the minus symbol is red.