Rewrote threaded log code to be more idiomatic.
[invirt/third/libt4.git] / rsm_client.h
index 583ecbb..2bdf440 100644 (file)
@@ -50,19 +50,19 @@ int rsm_client::call_m(unsigned int proc, R & r, const marshall & req) {
     string res;
     u >> res;
     if (!u.okdone()) {
-        LOG("failed to unmarshall the reply.");
-        LOG("You probably forgot to set the reply string in " <<
-            "rsm::client_invoke, or you may have called RPC " <<
-            "0x" << hex << proc << " with the wrong return type");
-        LOG("here's what I got: \"" << hexify(rep) << "\"");
+        LOG << "failed to unmarshall the reply.";
+        LOG << "You probably forgot to set the reply string in " <<
+               "rsm::client_invoke, or you may have called RPC " <<
+               "0x" << hex << proc << " with the wrong return type";
+        LOG << "here's what I got: \"" << hexify(rep) << "\"";
         VERIFY(0);
         return rpc_protocol::unmarshall_reply_failure;
     }
     if(!unmarshall(res, false, r).okdone()) {
-        LOG("failed to unmarshall the reply.");
-        LOG("You are probably calling RPC 0x" << hex << proc <<
-            " with the wrong return type.");
-        LOG("here's what I got: \"" << hexify(res) << "\"");
+        LOG << "failed to unmarshall the reply.";
+        LOG << "You are probably calling RPC 0x" << hex << proc <<
+               " with the wrong return type.";
+        LOG << "here's what I got: \"" << hexify(res) << "\"";
         VERIFY(0);
         return rpc_protocol::unmarshall_reply_failure;
     }