3 ms·

The behavior of C macros is actually described by a piece of pseudocode from Dave Prosser and it is not in the standard: * https://www.spinellis.gr/blog/200606

by chirsz 11mo ago

The behavior of C macros is actually described by a piece of pseudocode from Dave Prosser and it is not in the standard: * https://www.spinellis.gr/blog/20060626/ https://www.spinellis.gr/blog/20060626/ * https://www.spinellis.gr/pubs/jrnl/2006-DDJ-Finessing/html/Spi06j.htm https://www.spinellis.gr/pubs/jrnl/2006-DDJ-Finessing/html/S... * https://gcc.gnu.org/legacy-ml/gcc-prs/2001-q1/msg00495.html https://gcc.gnu.org/legacy-ml/gcc-prs/2001-q1/msg00495.html

viega 11mo ago
Wow, I'm not sure I've ever seen this (or if I did, it was 20 years ago). And I was definitely looking around for this kind of history when I was searching around when writing. Perhaps my google skills have decayed... or google... or both! Thanks very much.
- kragen 11mo ago
  Oh, are you L33 T.?
  - viega 11mo ago
    If my google fu is that bad, it's pretty much impossible to be.
    - kragen 11mo ago
      Oh, I understood you to be saying you'd written this article.
camel-cdr 11mo ago
This is the best explanation I've seen so far: https://marc.info/?l=boost&m=118835769257658&w=2 https://marc.info/?l=boost&m=118835769257658&w=2
- deleted 11mo ago
  [deleted]
- krackers 11mo ago
  This needs to be framed somewhere, very lucid explanation
kragen 11mo ago
Thank you very much for providing these links!
Joker_vD 11mo ago
Honestly, it feels like something like this should have been put in the standard instead of all the English prose that ended in the section about the preprocessor expansion. Yeah, it's not pretty, but at least it requires way less skill in hermeneutics to understand correctly.