Lorenzi

Sorry, @mmasdivins, I have been focusing on other projects recently. I don't know if I'll get around to doing it anytime soon, unfortunately.

That's certainly a good idea! I'll take a look and see if it's any easy to implement in the current architecture.

Yeah... This was by design, but it doesn't seem to have been the best idea. The idea is that whenever the referenced variable comes directly from the instruction parameters (i.e....

Yes! That was the original idea.

It should work! I mean I had this idea for a while, it's just unimplemented as of yet.

Hmm, in what case exactly are you encountering the hard error? I have a few test cases for `#fill`, but none of them are catching it. About it accepting any...

Could you give some syntax examples on the usage of `reg_a`? Is it to be used in a rule declaration, or among your user code?

How about something like: ``` #const REG_A_VALUE = 184`8 #subruledef register { %r{num: u8} => num reg_a => REG_A_VALUE } ``` You can easily redefine constants via a few methods:...

I see. To work around this on the current version, maybe you could declare your `#subruledef`s conditionally instead? Using one of the suggestions from my previous post. For example, declare...

Hmm, this might be unsolvable in the current architecture. The reason `s0 %r0` fails is that the `a` subrule `s{x: u4}` starts parsing an expression after the `s` token, and...