Date: Fri, 20 Sep 2019 13:26:37 -0400
On 30/08/2019 21.26, Michael Spencer via SG15 wrote:
> I've attached a paper I've written for the upcoming Denver SG15 meeting and
> the Belfast meeting.
>
> "This [...] is correct for standard C++ except for abuse of
> `__LINE__` such as `#if __LINE__ > 456`.
...and even then, presumably an implementation could keep track of
original line numbers which would let it handle such pathological cases.
BTW:
> The dependency scanner succeeds and then the compiler sees the code and
> i̴̝̍ĝ̸̠̳͚̻ņ̸̱̗̅́̾̐͠o̶̲̳̫͒͊͊ȑ̵̺̱͚̩͎͌͑͒̕e̸̗̾s̸̮̰̻̥͑̑͊̂̆ ̴̤͍̄ȉ̸̬͝m̵̞͈̿́p̷̢̛̣̹̒̑̽̀ǫ̴̜̖̱̈̏̈͝r̸̨̻̖̪̔̍̾ͅt̵̙̑s̸̩͎̜̼͑́̚ ̵̤̒͑ȩ̶̹̫̥͗̂r̵͍͈̦͗r̵̩̲̊̿͝ǫ̸̞̙́͊͐͗͗r̷̝̥̬̲͇̀͋̚s̷̰̠͙̤̉ͅ due to undefined behavior.
What on Earth happened here?
Anyway, thanks for the paper!
> I've attached a paper I've written for the upcoming Denver SG15 meeting and
> the Belfast meeting.
>
> "This [...] is correct for standard C++ except for abuse of
> `__LINE__` such as `#if __LINE__ > 456`.
...and even then, presumably an implementation could keep track of
original line numbers which would let it handle such pathological cases.
BTW:
> The dependency scanner succeeds and then the compiler sees the code and
> i̴̝̍ĝ̸̠̳͚̻ņ̸̱̗̅́̾̐͠o̶̲̳̫͒͊͊ȑ̵̺̱͚̩͎͌͑͒̕e̸̗̾s̸̮̰̻̥͑̑͊̂̆ ̴̤͍̄ȉ̸̬͝m̵̞͈̿́p̷̢̛̣̹̒̑̽̀ǫ̴̜̖̱̈̏̈͝r̸̨̻̖̪̔̍̾ͅt̵̙̑s̸̩͎̜̼͑́̚ ̵̤̒͑ȩ̶̹̫̥͗̂r̵͍͈̦͗r̵̩̲̊̿͝ǫ̸̞̙́͊͐͗͗r̷̝̥̬̲͇̀͋̚s̷̰̠͙̤̉ͅ due to undefined behavior.
What on Earth happened here?
Anyway, thanks for the paper!
-- Matthew
Received on 2019-09-20 12:28:46