VSIPL++ and Visual C++

[Wilson, Charles (cwilso11)]

From
http://www.codesourcery.com/public/vsiplplusplus/sourceryvsipl++-1.3/qui
ckstart/ch02s03.html, it is apparent that /building/ CodeSourcery
VSIPL++ requires the Intel C++ compiler. Once built, though, can the
library be used from Microsoft Visual C++ 2005?  If VSIPL++ were a C
library, the answer would obviously be yes because the ABI for C is
standardized and the header files contain little actual code.  However,
CodeSourcery VSIPL++ is C++, which makes for ABI issues between
compilers.  Also, it makes extensive use of templates and template
meta-programming techniques so quite a bit of the functionality is in
the public header files -- which the "client compiler" needs to process
to generate instantiated code.

So

(1) can a pre-compiled VSIPL++ library (such as the one here:
http://www.codesourcery.com/vsiplplusplus/1.3/download.html) be used
from Microsoft Visual C++ 2005 -- is MSVC 2005 "ISO C++ compliant"
enough?

(2) If so, then why can't VSIPL++ be /built/ using MSVC2005 -- assuming
that either individual licenses for IPP and MKL are obtained, or those
(presumably optional) elements are disabled when running configure.

(3) If not, the what is the point of using the /Qvc8 switch when
building VSIPL++ with the Intel C++ compiler? (Why worry about the MS
ABI if all clients of the library are required to icc anyway?)

Thanks,
Charles Wilson