Issue 18382: Implementation Dependent Input and Output should become optional (vsiplxx-rtf)
Source: Mentor Graphics Corporation (Mr. Stefan Seefeld, stefan(at)seefeld.name)
Nature: Enhancement
Severity: Minor
Summary: VSIPL and VSIPL++ both provide APIs to serialize certain objects. The VSIPL++ API supports serialization of blocks, while the VSIPL API supports serialization of function objects.


The API for both should be unified and made optional (a "profile"), as it is orthogonal to the rest of the spec.
Resolution: In the interest of closing the current RTF so that the solutions to resolved issues can be made publically available, this issue is deferred to the next RTF.
Disposition: Deferred
Revised Text: 
Actions taken:
January 22, 2013: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 22 Jan 2013 11:03:36 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-Tracker: AAAAAA==


*******************************************************************************
Name:            Stefan Seefeld
Employer:        Mentor Graphics
mailFrom:        stefan_seefeld@mentor.com
Terms_Agreement: I agree
Specification:   VSIPL
Section:          Implementation Dependent Input and Output
FormalNumber:    formal/12-12-01
Version:         1.4
Doc_Year:        Year
Doc_Month:       Month
Doc_Day:         Day
Page:            5.9
Title:           Implementation Dependent Input and Output should become optional.
Nature:          Enhancement
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


VSIPL and VSIPL++ both provide APIs to serialize certain objects. The VSIPL++ API supports serialization of blocks, while the VSIPL API supports serialization of function objects.


The API for both should be unified and made optional (a "profile"), as it is orthogonal to the rest of the spec.