Y-Less
Y-Less
I use several organisational tags, including ``, ``, and ``. It would be nice if these were properly hierarchical so that functions declared within one stayed within it. Better yet,...
@YashasSamaga You've looked in to this. Merge thoughts?
```diff source/compiler/sc1.c | 41 ++++++++++++++++++++++++----------------- 1 file changed, 24 insertions(+), 17 deletions(-) diff --git a/source/compiler/sc1.c b/source/compiler/sc1.c index a50409e..308da67 100644 --- a/source/compiler/sc1.c +++ b/source/compiler/sc1.c @@ -1982,25 +1982,30 @@ void sc_attachdocumentation(symbol *sym)...
That patch fixes this bug and also slightly more unifies the code between function and global pawndoc. Like why was the length modification for global comments done outside the `length...
Leaving this open until I merge.
That's a tricky one. Yes, it should be stock, but it's almost pointing at the wrong place for the mistake. Anyone getting the warning now is likely to look through...
Possibly, but then you get the opposite problem - people not getting data compiled that they expect to be compiled, and no warning for a variable without `stock` that isn't...
> Not sure what you mean by that exactly. If the data isn't used - it's not needed, so it shouldn't really matter if it's present in the binary file...
> That's how the compiler currently works, that won't change. Oh, so it is. In that case carry on.
I like it (though it's not solely up to me). Some sort of `-Wall` flag. You mentioned using `#pragma` to enable them, but a flag to turn them all on...