[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vsipl++] Token Issue with Intel's MKL and Boost 1.35

To: Brad Howes <howes@xxxxxxxxxx>
Subject: Re: [vsipl++] Token Issue with Intel's MKL and Boost 1.35
From: Stefan Seefeld <stefan@xxxxxxxxxxxxxxxx>
Date: Fri, 11 Jul 2008 11:01:38 -0400

Brad,

thanks for the report. The issue of global namespace pollution throughincluded third-party libraries (headers) is on our radar. For somelibraries we were successful in hiding these headers from the user byonly including them in .cpp files, but not publicly visible headers.

I'm not sure whether this is possible for MKL, too. We will look into this.

Thanks,
		Stefan

--
Stefan Seefeld
CodeSourcery
stefan@xxxxxxxxxxxxxxxx
(650) 331-3385 x718

References:
- [vsipl++] Token Issue with Intel's MKL and Boost 1.35
  - From: Brad Howes

Prev by Date: [vsipl++] Token Issue with Intel's MKL and Boost 1.35
Next by Date: [vsipl++] [patch] SSAR application - add capability to read little-endian files on big-endian systems
Previous by thread: [vsipl++] Token Issue with Intel's MKL and Boost 1.35
Next by thread: [vsipl++] [patch] SSAR application - add capability to read little-endian files on big-endian systems
Index(es):
- Date
- Thread

Actions

Re: [vsipl++] Token Issue with Intel's MKL and Boost 1.35