c++ - MSVC - Suppress template being compiled with messages -

-

i have application uses numerous templates , template specializations, , during msvc compilation many messages output showing how templates being compiled. makes incredibly difficult time finding actual compilation error. these messages not output when application compiled on linux using g++. 

    c:\program files (x86)\microsoft visual studio 12.0\vc\include\map(382) : see reference function template instantiation 'std::pair<std::_tree_iterator<std::_tree_val<std::_tree_simple_types<std::pair<const _kty,_ty>>>>,bool> std: :_tree<std::_tmap_traits<_kty,_ty,_pr,_alloc,true>>::insert<std::pair<std::string,uint64_t>>(_valty &&)' being compiled         [         _kty=std::string ,            _ty=size_t ,            _pr=std::less<std::string> ,            _alloc=std::allocator<std::pair<const std::string,size_t>> ,            _valty=std::pair<std::string,uint64_t>     ]

is there way can suppress these more or less useless messages? or possibly lower verbosity setting? i've tried looking @ link i'm not sure if there flag relates messages i'm seeing.

the message related warning (or error) specific template instantiation. if warning, suppress (via #pragma warning, or project settings), , message go away. or, fix cause of warning. there no way suppress message without suppressing warning, because without it, warning doesn't make sense.


Comments

Post a Comment

Popular posts from this blog

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co
Read more

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall
Read more

java - Cannot secure connection using TLS -

-
i'm trying establish secure socket connection between java client applet (built jdk 1.7.0_75-b13) , vc++ server application. as test vehicle, used vc++ client/server sample found in msdn forums, modified use schannel , able establish socket using cipher suite tls_rsa_with_aes_128_cbc_sha. works of tls 1.0/1.1/1.2. when try opening socket java applet same server application, connection rejected server reporting following: tls 1.0 acceptsecuritycontext failed: 0x80090327 tls 1.1 acceptsecuritycontext failed: 0x80090331 tls 1.2 acceptsecuritycontext failed: 0x80090331 this java code used create socket: debugprint("setting secure connection"); sslsocketfactory sslsocketfactory = (sslsocketfactory) sslsocketfactory.getdefault(); sslsocket sslsocket = (sslsocket) sslsocketfactory.createsocket("127.0.0.1", socketnumber); debugprint("starting handshake"); sslsocket.settcpnodelay(true); sslsocket.setsolinger(false, 0); sslsocket.s
Read more