[Jay_]

There are a couple of points in this topic that I disagree with.

Is there any evidence to suggest the use of stock has any impact on the code or performance whatsoever?

It was highlighted in a previous post that prefixing functions with "stock" is useful for searchability which is an important thing when we have such limited IDE's for PAWN.
Yes, you can add preprocesser defines for "function", but if the use of stock doesn't make a difference, why bother? Also, "function" is a very broad term - what about callbacks or mutator methods?

Quote:

Originally Posted by Vince Is the function or variable for internal use only? If yes, use static. Is the function or variable for internal use only, but is there a chance that it may not be used (conditional compiling)? If yes, use static stock

Perhaps you need to elaborate on the term "internal" here. The static keyword will bind a function/variable to the specific file that it is being declared in (think of it as the private access modifier).
One could argue that in the context of which you're using this term, filterscripts or gamemodes which may consist of many different files would be classed as "internal" as they're not includes.