Issue 18188: VSIPL and VSIPL++ should define version macros (vsiplxx-rtf) Source: (Mr. Brooks Moses, brooks.moses(at)dpdx.net) Nature: Enhancement Severity: Minor Summary: The VSIPL++ (and VSIPL) standards should define version macros, so that application code can be conditionalized on what version of the library they are being compiled with. This should be done with numeric macros (i.e., VSIP_VERSION=1 and VSIP_VERSION_MINOR=2) to enable numeric comparisons. In addition, there should be separate macros for VSIPL and VSIPL++, and either there should be separate version macros for VSIPL++ and Parallel VSIPL++, or there should be a macro ("VSIP_PARALLEL"?) to indicate whether the Parallel VSIPL++ pieces are supported. Resolution: Revised Text: Actions taken: October 19, 2012: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 19 Oct 2012 19:32:16 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Brooks Moses Employer: Mentor Graphics mailFrom: brooks_moses@mentor.com Terms_Agreement: I agree Specification: VSIPL++ Section: 3.1 Macros FormalNumber: ptc/2012-07-27 Version: 1,2 - FTF Beta 1 Doc_Year: 2012 Doc_Month: August Doc_Day: 10 Page: 7 Title: VSIPL and VSIPL++ should define version macros Nature: Enhancement Severity: Minor CODE: 3TMw8 B1: Report Issue Description: The VSIPL++ (and VSIPL) standards should define version macros, so that application code can be conditionalized on what version of the library they are being compiled with. This should be done with numeric macros (i.e., VSIP_VERSION=1 and VSIP_VERSION_MINOR=2) to enable numeric comparisons. In addition, there should be separate macros for VSIPL and VSIPL++, and either there should be separate version macros for VSIPL++ and Parallel VSIPL++, or there should be a macro ("VSIP_PARALLEL"?) to indicate whether the Parallel VSIPL++ pieces are supported. Thanks, - Brooks