4 ms·
Straw man. When was the last time you had to check the documentation for the parameter evaluation strategy of a C function call? I don't think it is a controve
by brandonbloom 10y ago
Straw man. When was the last time you had to check the documentation for the parameter evaluation strategy of a C function call?
I don't think it is a controversial statement than a badly designed macro can do more damage than a badly designed function. I believe that this is true, even normalizing for bad macro systems. This is not a statement against macros, so much as it is a statement to consider when making tradeoffs.
- lisper 10y agoWhat would you cite as an example of a badly designed macro?
- lisper 10y agoIt is controversial. The GETS function is probably responsible for a huge number of security breaches with a cost possibly ranging into the billions of dollars (there's no way to really know). What would you cite as a comparable example of a badly designed macro?
- GFK_of_xmaspast 10y agoPart of the reason gets() has been such a disaster is that people use it.