Y-Less
Y-Less
```pawn #pragma unused end ``` Doesn't seem to bypass the warning. I think it should.
OK, I think the first one for `end` is not applicable, turns out it was right - it was referring to the clobbered write there. The second is still true...
Putting it before makes sense. But maybe the message could be improved a bit, because I merged the PR and keep getting caught out. The problem is: ```pawn h =...
I'm not sure how to classify this, because the compiler is sort of right. `#` at the start of a line is used for pre-processor directives, so that's how it...
The only directives I've wanted mid-function are in some case like: ```c Function( long, list, of, complex, parameters, #if COMPILE_OPTION 1 #else 2 #endif ); ``` Yes, there are other...
I'd say fill it with 0s. That's already the way other arrays work when you don't specify everything: ```pawn new arr[10] = {1, 2}; ```
I should, but I don't test on Linux as much as I should.
Those missing specifier rules are causing YSI to stop building. I know I usually say that breaking YSI isn't a blocker for new compiler versions because it does a lot...
I'm actually not sure what the most sensible result is here. It seems there are equally good arguments for "all specifiers are additive", so this declares a `static stock` function:...
There is another option - remove old-style declarations, but that's a bigger change.