Moony
Moony
Could possibly add a anti-pattern warning that is printed when someone does something like `#define foo 0x1214` and advise using `foo = 0x1214` But if that's done, i'd recommend first...
for now, I recommend doing what GAS does: Run the C preprocessor over the file, _assuming_ that works I've done that for an _entirely custom assembler_, where I could guarantee...
An easy way to forbid cycles is to have a maximum substitution depth, which also handles a bunch of other related issues, so it's what I'd probably go with.
> Why can't you forbid the user to expand not yet defined macros or recursive macros? This would guarantee termination. Recursive behavior and deep substitution has it's genuine uses, so...
#489 is merged now, however there is very little documentation on how to _use_ it.
It's been five years. Isn't it about time this is un-postponed?
A better suggestion would be f16 support, as it is common in graphics.
@elecprog x87 is no longer the normal case. They're stored as is in SIMD registers, x87 has been out of use for over a decade. SIMD directly operates on 64-bit...
This, please. Right now i'm adding OC directly to the pack manually, without it being properly integrated into the pack.
> By iff console do you mean mass scanner or shuttle console? They mean the IFF console.