torque-asm, branch v2.5.0Lightweight meta-assemblerhttps://code.benbridle.com/torque-asm/atom?h=v2.5.02025-04-27T04:17:57ZUpdate version to 2.5.02025-04-27T04:17:57ZBen Bridleben@derelict.engineering2025-04-27T04:17:57Zurn:sha1:3fe1a4f983904340d8bac580164b3862376d7acfImplement <abs> operator for expressions2025-04-27T04:17:32ZBen Bridleben@derelict.engineering2025-04-27T04:17:32Zurn:sha1:058938fed4562d4802c7b7d8dc52524dbde354cb
The <abs> operator returns the absolute value of an integer.
Update assembler and log libraries2025-04-27T00:42:28ZBen Bridleben@derelict.engineering2025-04-27T00:41:59Zurn:sha1:a417f9b6440871bbec26520f0921189ee156e9ff
This update replaces all uses of the ansi library with the new inked
library. This means that terminal colours will now be handled correctly
under Windows.
Update version to 2.4.02025-04-26T02:47:21ZBen Bridleben@derelict.engineering2025-04-26T02:47:21Zurn:sha1:9dd8608b300d0984a018ed888039506dc886fa4aAllow label references in pinned address calculations2025-04-26T02:45:05ZBen Bridleben@derelict.engineering2025-04-26T02:44:50Zurn:sha1:50592a5184e701dd09eee024bb773ec57c1cd6bf
This is a relaxation of the rule where a label reference could not
be used in any context that could change the length of an assembled
program.
We implement this in the bytecode stage by naively calculating an
initial address for each label as before. If a pinned address is
calculated from a label reference, some of the calculated addresses
could be incorrect. We then attempt to run the bytecode stage, which
will calculate a more accurate address for each label based on how
pinned addresses are calculated. If the address of any label was
changed by running this stage, we re-run the stage up to three more
times until all labels stabilise. If the labels fail to stabilise, we
return an error.
Implement first-class string literals2025-04-26T01:00:51ZBen Bridleben@derelict.engineering2025-04-26T01:00:51Zurn:sha1:e5447e2568e24db9a5218bbe452b856266ca39ae
This feature promotes strings to a first-class type in the language.
If a string is passed to an invocation via the new string-type argument,
the string will be passed as a whole value. String arguments can still
be passed to an invocation via an integer-type argument, in which case
they'll be broken apart into individual characters with the macro being
invoked once per character.
String-type macro arguments are declared like "name".
Fix misleading error message2025-04-25T21:31:58ZBen Bridleben@derelict.engineering2025-04-25T21:30:24Zurn:sha1:83e5107684a37aa825d626c19a2af7fd6bfc231a
The code here is really expecting a block value, but has received an
integer value. This catches the case where an integer value is
incorrectly included in a macro definition body alongside block tokens.
Implement <tal> operator for expressions2025-04-25T21:09:59ZBen Bridleben@derelict.engineering2025-04-25T21:09:59Zurn:sha1:4b53479153806e3a1e7a4944313f77dc262117b2
The <tal> operator returns the number of set bits in the binary
representation of an integer. For negative numbers, only a single sign
bit is counted in the result.
Add a rust-toolchain file2025-04-25T20:28:17ZBen Bridleben@derelict.engineering2025-04-25T20:27:47Zurn:sha1:8c30c7fbe9b869fb78765a4b7994858f0c8f8182
This file will make the project build with the nightly toolchain by
default, which will make building the project slightly easier for other
people.
Update version to 2.3.02025-04-18T08:48:26ZBen Bridleben@derelict.engineering2025-04-18T08:48:26Zurn:sha1:23d61c0a0192dac7e79cb42c71a3efff705f19c6