Jump to content
Sign in to follow this  
  • entries
    88
  • comments
    117
  • views
    62394

Biggest single error message ever?

Sign in to follow this  
dcosborn

300 views

../src/res/load.cpp:37: error: request for member 'push_back' in '((page::res::<
unnamed>::LoadersMap*)page::res::::GetLoadersMap())->std::tr1::unordere
d_map const std::string&), std::allocatorst std::string&)> >, std::tr1::hash, std::equal_tostd::type_info*>, std::allocatortorconst void* (*)(const page::res::Pipe&, const std::string&)> > > >, false>::nymous>.std::tr1::hashtable RehashPolicy, cache_hash_code, constant_iterators, unique_keys>::insert [with K
ey = const std::type_info*, Value = std::pairvectoror > >, Allocator =
std::allocator*)(const page::res::Pipe&, const std::string&), std::allocatoronst page::res::Pipe&, const std::string&)> > > >, ExtractKey = Internal::extrac
t1stge::res::Pipe&, const std::string&), std::allocatorres::Pipe&, const std::string&)> > > >, Equal = std::equal_tofo*>, H1 = std::tr1::hash, H2 = Internal::mod_range_hashi
ng, H = Internal::default_ranged_hash, RehashPolicy = Internal::prime_rehash_pol
icy, bool cache_hash_code = false, bool constant_iterators = false, bool unique_
keys = true](((const std::pairid* (*)(const page::res::Pipe&, const std::string&), std::allocator(*)(const page::res::Pipe&, const std::string&)> > >&)((const std::paird::type_info* const, std::vectortd::string&), std::allocatorstring&)> > >*)(& std::pair (*)(const page::res::Pipe&, const std::string&), std::allocator(const page::res::Pipe&, const std::string&)> > >(((const std::type_info* const&
)((const std::type_info* const*)(&((const std::type_info*)type)))), ((const std:
:vectortor >&)((const std:
:vectortor >*)(& std::vect
oronst void* (*)(const page::res::Pipe&, const std::string&)> >(((const std::alloc
ator&)((const std::
allocator*)(& std::
allocator()))))))))
)))).std::pairt, std::vector:allocator > >, fal
se, false>, bool>::second', which is of non-class type 'bool'
Can you do better?
Sign in to follow this  


1 Comment


Recommended Comments

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!