tree 15bb60d52fe7ba64da849944566b3667758b88f3
parent a1ef754a6d47d1497396306f43aa1d1201065e13
author Willy Tarreau <w@1wt.eu> 1605725625 +0100
committer Willy Tarreau <w@1wt.eu> 1605725978 +0100
encoding latin1

DOC: coding-style: update a few rules about pointers

It's really annoying to see that in 2020 we're still facing bugs caused
by dangling pointers in the code that result from poorly written rules
about how these pointers are supposed to be handled, set and reset. Let's
add a few supposedly obvious (but apparently not) rules about how pointers
have to be used through out the code in hope to make such bad practices
disappear (or at least have something to point the authors to after
reviewing their code).