SoylentNews is people
SoylentNews
https://www.cossacklabs.com/blog/macros-in-crypto-c-code.html
Like death and taxes, one thing that you can be sure of is that using C macros in a modern software project will cause a debate. While for some macros remain a convenient and efficient way of achieving particular programming goals, for others they are opaque, introduce the unnecessary risk of coding errors, and reduce readability.
The criticism of macros is particularly acute in the wider security community. Among Cossack Labs' engineers and the core Themis crypto library contributors there are people who previously worked on auditing cryptographic implementations of critical code. Their typical knee-jerk reaction to macros was always "kill it with fire and never use it again". Taking no sides, we would like to assess both pros and cons of using such dangerous things as macros in security code (as we faced the issue when developing Themis) and suggest some techniques for lowering the accompanying risks.
We'll also discuss a custom "for-audit" build target for Themis designed specifically to generate source code that exposes the macros to inspection because we appreciate the need for security software to be subject to detailed source code scrutiny.
(Score: 2) by theluggage on Saturday December 02 2017, @04:10PM
Well, that's no harder than looking up what a macro does, and by using a function you can define the types of the arguments and the return value so they get checked, and it avoids sneaky side effects that you can get by using "++" or "&" in a macro so suddenly it can change your parameters. Back in the good old days, using a macro rather than a function call would save you a bunch of clock cycles - in 2017, clock cycles are cheap, and it should be the compiler's job to optimise your code by automatically inlining functions.