At compilation - yes, that sounds good.
For strict, it would be easier to do (from a users point of view) if it was a project setting that is applied to all files in that project. If you leave it OFF by default when creating a project compile and warn as normal. If the project setting is changed to ON convert those warnings into errors.
For strict, it would be easier to do (from a users point of view) if it was a project setting that is applied to all files in that project. If you leave it OFF by default when creating a project compile and warn as normal. If the project setting is changed to ON convert those warnings into errors.