On Thu, Jul 26, 2018 at 09:57:42AM -0700, Junio C Hamano wrote: > Jeff King <peff@xxxxxxxx> writes: > > > On Wed, Jul 25, 2018 at 03:13:37PM -0700, Junio C Hamano wrote: > > > >> * jk/banned-function (2018-07-24) 5 commits > >> - banned.h: mark strncpy() as banned > >> - banned.h: mark sprintf() as banned > >> - banned.h: mark strcat() as banned > >> - automatically ban strcpy() > >> - Merge branch 'sb/blame-color' into jk/banned-function > >> > >> It is too easy to misuse system API functions such as strcat(); > >> these selected functions are now forbidden in this codebase and > >> will cause a compilation failure. > >> > >> Will merge to 'next'. > > > > Eric nudged me over the fence to use a slightly different mechanism to > > generate the error. See: > > > > https://public-inbox.org/git/20180726072105.GA6057@xxxxxxxxxxxxxxxxxxxxx/ > > > > It looks like sb/blame-color graduated, so this could also just be > > applied directly on master now to avoid the funky merge. > > OK. Is it that "you cannot call a variable" thing? We don't try to call it, but rather just mention it. It's just that the compiler is more strict about undeclared variables than it is about undeclared functions. -Peff
