Timeline for typedefs and #defines
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 18, 2012 at 11:31 | comment | added | Joris Timmermans | @c0da - you should not be using macros for typedefs, you should be using typedefs for typedefs. The actual effect of the macro can be very different, as illustrated by various responses. | |
| Jan 18, 2012 at 11:29 | comment | added | Tamás Szelei | Yes, but it's not about shortness. A macro can do a zillion other things besides typedefing. But personally I think scoping is the most important. | |
| Jan 18, 2012 at 11:27 | comment | added | c0da | But as I have shown in the example provided in the question, a typedef and #define use the same number of words! Also, these 3 words of a macro won't cause any confusion, as the words are the same, but just rearranged. :) | |
| Jan 18, 2012 at 11:18 | history | answered | Tamás Szelei | CC BY-SA 3.0 |