Y-Less

Well maybe, but I don't think that really addresses the root issue, that's just a patch for one symptom.

https://wiki.alliedmods.net/SourcePawn_Transitional_Syntax#Methodmaps

I think I've solved the pre-processor issue: `__tagof()`. This is basically a pre-processor-time version of `tagof()`, which returns the tag as a symbol. Thus: ```pawn this.Func() ``` Becomes: ```pawn __tagof(this)Func(this)...

We just need to be careful not to parse `this` (or any other symbol) multiple times in the pre-processor, to avoid possibly incorrect macro replacements. I.e. replacing it once when...

It would be much easier to blacklist uses, rather than whitelist them. I don't think there are any others besides these: ```pawn if (uninitialised) // warning ``` ```pawn FuncNotPassedByRef(uninitialised) //...

I don't think we should worry about people not using the latest versions of things on the latest version of something. If they want to use the new compiler, but...

I merged this and had a play. It is somewhat telling that when I tested this on YSI with tests enabled almost every warning instance was `i`, `idx`, `pos` or...

Also a definite bug. If this PR is merged to HEAD now, I get: ``` YSI_Core\y_core\y_utils_impl.inc(597) : warning 214: possibly a "const" array argument was intended: "str" ``` On: https://github.com/pawn-lang/YSI-Includes/blob/771b7b027cad95da1ec4210b9791eddf7b3b97d3/YSI_Core/y_core/y_utils_impl.inc#L597...

I'm still slightly wary of this, so I'd like to know what others think. @Zeex @Southclaws @YashasSamaga etc? I just checked again and there are several places in YSI that...

> > > > Maybe it should be restricted only to variables whose first use is a read outside of a loop in which they are modified. > > Sounds...