Peter-Jacob
Peter-Jacob
Look, I’m retired from thinking — now I just code. No architecture, no strategy. Just keyboards and caffeine. Tell me what you need, I’ll get it done. If it’s nonsense,...
The conversion functions seem to have a general underlying issue: they operate at the byte level. However, CREXX strings are UTF-8 encoded, meaning a single character may consist of one...
If you point me to Josep's additions, I can have a look!
This is an experiment on how we could handle C2X more generically by respecting the actual byte length of UTF-8 characters: ``` 138: René: 52656ec3a9 138: Rene: 52656e65 138: Adrian:...
Here is the assembly: I removed the value function (which is internally used to reflect changes in meta_clear). If I understand correctly, no procedure frame is used to extract the...
Please help me understand this code. From what I gather, the `metalloadcalleraddr and linkattr` instructions address the caller's procedure frame. I initially assumed that iterating through all existing addresses in...
First, we need to distinguish the standard VALUE function from Regina's version. In the standard implementation, VALUE retrieves the content of a variable provided as a parameter. Your initial version...
Fully agree, let's postpone it for level c
Introducing a dedicated binary type feels like overkill, given how limited its actual use case appears to be. If we restrict the UTF-8 string to just the characters 0–9 and...