alx-0014 - Refactor syntax of preprocessing directives

[alejandro-colomar]

Closes: #8249

Cc: @jwakely , @jensmaurer

[alejandro-colomar]

I wasn't able to build the draft PDF locally, so this is untested.

[alejandro-colomar]

@jwakely , @jensmaurer

I recommend reviewing these commits with git-show(1)'s --color-moved, which shows that all of this is moving text around, with no real changes (other than the additions of *-directive syntax entries, of course).

Is it okay like this? Or do you prefer it squashed in one commit?

(I wish github had this --color-moved in the WebUI. Actually, I wish I wasn't using github. :) )

[alejandro-colomar]

Ping. :)

[AlisdairM]

As we are in the ballot resolution period for the C++26 standard, I would not be waiting too eagerly for a change of this scale to be reviewed in the next six months or so. I might happen, as we want to produce the highest quality standard that we can, but we also have significant work to resolve NB concerns and publish the completed standard that clearly have our undivided attention until then.

[alejandro-colomar]

As we are in the ballot resolution period for the C++26 standard, I would not be waiting too eagerly for a change of this scale to be reviewed in the next six months or so. I might happen, as we want to produce the highest quality standard that we can, but we also have significant work to resolve NB concerns and publish the completed standard that clearly have our undivided attention until then.

Thanks! That's useful info to me. :)

Cheers,
Alex