5

We're trying to use http://cpp-netlib.org and failing to compile it, because in one of its headers it has:

namespace network {
    namespace utils {
        struct thread_pool;
    }
}

and in another:

namespace network {
        namespace utils {
            typedef ::network::concurrency::thread_pool thread_pool;
    }
}

From what I understand from Forward declaration of a typedef in C++ and http://www.cplusplus.com/forum/beginner/75561 in C++ this is basically illegal - you just can't forward declare: "struct A;" and then try to "typedef X A;".

So, my question is, what on earth might they be compiling this with that allows it? Is this some new feature of C++11, since they are claiming to use the latest-greatest-of-C++11?

Community
  • 1
  • 1
DeducibleSteak
  • 1,398
  • 11
  • 23

1 Answers1

4

this is basically illegal

Yes, it is.

So, my question is, what on earth might they be compiling this with that allows it?

Perhaps, they never include both headers in the same translation unit. In that case most compilers won't be able to diagnose the error (which isn't required to be diagnosed); and there's a chance that you'll still end up with a working program. You're definitely in the world of undefined behaviour, though.

Is this some new feature of C++11?

No. You can do various interesting things with using to create aliases; but you still can't declare a type as both a class and a typedef.

Mike Seymour
  • 249,747
  • 28
  • 448
  • 644
  • This is very unlikely to really work. The translation unit that sees the type will mangle names that use that type as `::network::utils::thread_pool`, but the translation unit that sees the `typedef` will mangle with `::someother::namespace_::andtype`, I doubt the linker would not barf at that – David Rodríguez - dribeas Sep 27 '13 at 15:37