Top Tweets for #include_next

Steve Downey @sdowney

over 4 years ago

@AaronBallman @RyanSalsamendi @__phantomderp There's also fun where some filesystem doesn't support links and 'the same' file is now in two places when synced locally. The joy where '/path/link/..' isn't the same as '/path' and there's a #include "../I_know_what_I_am_doing.h" #include_next fun file inclusion is awful.

0

0

0

0

0

Steve Downey @sdowney

over 4 years ago

@__phantomderp @jcelerie Very quirky like NFS, which is common. That includes clearcase (which I hate, but). #include_next causes additional headaches, too. Not standard, just necessary.

0

1

0

0

0

🔺 TriΔng3l 🔺 🐸 @Triang3l

almost 5 years ago

> #include_next <string.h> WHO'S THAT POKÉMON??????? 😱

1

1

0

0

0

Andy Hippo @werat

almost 5 years ago

TIL about #include_next pragma which basically says “yeah, include lib.h, but not this lib.h, another one!” and I think that’s beautiful

0

1

1

0

0

Carl Dong → obscura.com

over 6 years ago

This Halloween, I’m going as an #include_next which breaks all your builds >= GCC 6

Carl Dong → obscura.com

over 6 years ago

Seriously considering writing a gcc/clang wrapper that just uses grep and find to JUST FIND THE RIGHT HEADERS IN THE RIGHT ORDER GOSH DARN IT

1

9

0

0

0

0

3

0

0

0

over 9 years ago

#include_next ...

0

0

0

0

0

ケケモコソカメニハ @ytomino

almost 10 years ago

@masterq_mogumog -Iでサブディレクトリを指定されたりは慣習上無いとは思いますが、#include_next がありますからユニークというのはどうでしょう？

2

0

0

0

0

��𝙖𝙣𝙞𝙩𝙩𝙖/𝙩𝙧𝙞𝙩 @trit_techne

over 10 years ago

あと http://t.co/3b0FoPmeTV の #include_next <inttypes.h>ってどれ呼び出してるんだろ．再帰？？それともclang以外のinttypes.h??

2

0

0

0

0

Last Seen Hashtags on Sotwe

Trends for you

Most Popular Users