[cpp.pre] Footnote makes unsupported claim that preprocessing directives are commonly called "lines"

[zygoloid]

[cpp.pre]/2 contains this footnote:

117. Thus, preprocessing directives are commonly called “lines”. These “lines” have no other syntactic significance, as all whitespace is equivalent except in certain situations during preprocessing (see the # character string literal creation operator in [cpp.stringize], for example).

I can find no evidence to refute the claim that this footnote is the only place in all of human history that the term "lines" has been used to refer specifically to preprocessing directives. I dispute that this is "common".

Also, all of raw string literals, escaped newlines, and newlines within /*...*/ comments allow preprocessing directives to span what would be "commonly called" multiple lines. Is this footnote really adding value?

[Halalaluyafail3]

This footnote appears in C too, and has been there since first standardization.

[eisenwave]

It doesn't make much grammatical sense, but it sounds to me like it's trying to describe what constitutes lines of code (before or after preprocessing), even though it's phrased like a definition of "line" as being a preprocessing directive.

I would be fine with deleting the footnote if we have any other place that says what a line is, such as for the purpose of source_location.

[jensmaurer]

The footnote is attached to the definition of a "preprocessing directive"; usual lines of code are not that. The footnote should go.