🔒 Locked

Whats problem with using vectorstring ??

Started by johnnyBravo Jun 28, 2004 at 10:49 PM 1 replies 350+ views

Original Post

141

Jun 28, 2004 at 10:49 PM

Hi im using vector name; but the compiler returns 2 warnings. the warning messages only appear when i put the string with the vector. Anyway to stop this? , thanks

Quote:
ompiling... mapper.cpp c:\program files\microsoft visual studio\vc98\include\vector(60) : warning C4786: 'std::reverse_iterator,std::allocator > const *,std::basic_string,std::allocator >,std::basic_string,std::allocator > const &,std::basic_string,std::allocator > const *,int>' : identifier was truncated to '255' characters in the debug information c:\program files\microsoft visual studio\vc98\include\vector(58) : while compiling class-template member function '__thiscall std::vector,std::allocator >,std::allocator,std::allocator > > >::~std::vector,std::allocator >,std::allocator,std::allocator > > >(void)' c:\program files\microsoft visual studio\vc98\include\vector(60) : warning C4786: 'std::reverse_iterator,std::allocator > *,std::basic_string,std::allocator >,std: :basic_string,std::allocator > &,std::basic_string,std::allocator > *,int>' : identifier was truncated to '255' characters in the debug information c:\program files\microsoft visual studio\vc98\include\vector(58) : while compiling class-template member function '__thiscall std::vector,std::allocator >,std::allocator,std::allocator > > >::~std::vector,std::allocator >,std::allocator,std::allocator > > >(void)' Linking... Mapper.exe - 0 error(s), 2 warning(s)

TangentZ

Jun 28, 2004 at 10:54 PM

Let's see... VC++6... Debug build?

#pragma warning(disable:4786)

Just put that line before #include . This warning
is harmless and can be safely ignored.

Fruny

203

Fruny

Jun 28, 2004 at 10:55 PM

"identifier was truncated to '255' characters in the debug information"

It's a spurious warning due to limitations of the VC6 debugger.
Feel free to ignore it, or to disable it with a #pragma warning(disable: 4786) placed before your the #include for the components that trigger the warning (here and ).

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.