26.07.2018, 11:51
Stock suppresses the warning when a function isn\'t used.
If you are writing a library, you are providing a set of optional functions to do different things. For any given use, not all of those functions may be required, thus a warning would be annoying. Hence stock in libraries.
If you are writing a mode, that is a single set piece of functionality. Everything is there for a reason and should do something. If you have a function in a mode that isn\'t used that\'s a mistake. Thus without stock the compiler will point out your mistake so you can either call it or remove it.
So yes, using stock in a mode is objectively wrong, it isn\'t just the opinion of a few members.
If you are writing a library, you are providing a set of optional functions to do different things. For any given use, not all of those functions may be required, thus a warning would be annoying. Hence stock in libraries.
If you are writing a mode, that is a single set piece of functionality. Everything is there for a reason and should do something. If you have a function in a mode that isn\'t used that\'s a mistake. Thus without stock the compiler will point out your mistake so you can either call it or remove it.
So yes, using stock in a mode is objectively wrong, it isn\'t just the opinion of a few members.