Possible fix for an OpenSolaris "pureparm" compilation error.

Our CallJobHere1() macro tried to help the compiler to determine the right
JobMemFun() profile by explicitly specifying the first JobMemFun() template
argument type. There is a second template argument in the CallJobHere1 case,
but we cannot specify it explicitly. Apparently, OpenSolaris compiler got
confused, perhaps justifiably so, by only one template argument specified.

This change removes the explicit first template parameter from the JobMemFun()
call inside the CallJobHere1(). It does not seem to be required for GCC on
RHEL5.  Tests will show what other compilers think.

diff --git a/src/base/AsyncJobCalls.h b/src/base/AsyncJobCalls.h
index ef9a285f4ba5edc0a55a0e40a86e3e58ee2af6c5..23434a1a1a0a092c37fa3062f5433d3a19a9d83f 100644 (file)
--- a/src/base/AsyncJobCalls.h
+++ b/src/base/AsyncJobCalls.h
@@ -59,7 +59,7 @@ CallJob(int debugSection, int debugLevel, const char *fileName, int fileLine,
 #define CallJobHere1(debugSection, debugLevel, job, Class, method, arg1) \
     CallJob((debugSection), (debugLevel), __FILE__, __LINE__, \
         (#Class "::" #method), \
-        JobMemFun<Class>((job), &Class::method, (arg1)))
+        JobMemFun((job), &Class::method, (arg1)))
 
 
 /// Convenience macro to create a Dialer-based job callback