Issues for Mailing list of the VSIPL 1.4 and VSIPL++ 1.2 (vsipl) Finalization task Force

To comment on any of these issues, send email to vsiplxx-ftf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 17402: Regarding mars/12-03-38 (VSIPL++ RFC Package
Issue 17403: Conformance statement
Issue 18198: "this header is usually included" should be excluded
Issue 18200: VSIPL reference in VSIPL++ is outdated
Issue 18214: Default value of Dense map type not described
Issue 18257: Compliance section needed
Issue 18258: Code examples in separate machine-readable file?
Issue 18260: Numbered sections?
Issue 18262: Minor font issue
Issue 18263: Another minor font issue
Issue 18266: Integrate addenda into main body of specification

Issue 17402: Regarding mars/12-03-38 (VSIPL++ RFC Package (vsiplxx-ftf)

Click here for this issue's archive.
Source: Unisys (Dr. Doug Tolbert, dtolbert408(at)gmail.com)
Nature: Uncategorized Issue
Severity:
Summary: 
Please update the inventory document (mars/12-03-12) to follow the URL naming and other conventions outlined in OMG document ab/07-06-01.

Resolution: A new and conforming inventory document supersedes the original one.
Revised Text:
Actions taken:
May 29, 2012: received issue
April 1, 2013: closed issue

Issue 17403: Conformance statement (vsiplxx-ftf)

Click here for this issue's archive.
Source: Unisys (Dr. Doug Tolbert, dtolbert408(at)gmail.com)
Nature: Revision
Severity:
Summary: 
Please collect all conformance information from various locations in mars/12-03-09 into a single conformance statement in section 1.3 as discussed at the March 2012 AB meeting

Resolution: The specification contains conformance criteria for (almost) each function definition. It is therefore not feasible to move them all into a single section. Instead, the existing conformance section has been amended with paragraphs outlining these criteria generically, to help the reader find those conformance points easily. New items 1.3/1 and 1.3/2 (page 1): 1. Most functions in this specification are parametrized for the value-types they operate on. The individual function specifications indicate which value-types need to be supported in a compliant implementation. 2. Compliance criteria relating to the VSIPL++ Parallel specification are listed in [dpp.oplevel]
Revised Text:
Actions taken:
May 29, 2012: received issue
April 1, 2013: closed issue

Issue 18198: "this header is usually included" should be excluded (vsiplxx-ftf)

Click here for this issue's archive.
Nature: Revision
Severity: Minor
Summary: 
These sections contain phrases like, "Note: This header file is usually
included in other header files so direct inclusion is rarely necessary."


This is non-normative, and because "usually" means "some implementations
may not do this", it is not helpful to users in writing
standard-conformant code.  In fact, it encourages users to write
non-comforming code!  These should be removed.

Resolution: The following note has been removed from item 4/1 (page 11): “[Note: This header file is usually included in other header files so direct inclusion is rarely necessary.]”
Revised Text:
Actions taken:
October 23, 2012: received issue
April 1, 2013: closed issue

Issue 18200: VSIPL reference in VSIPL++ is outdated (vsiplxx-ftf)

Click here for this issue's archive.
Nature: Revision
Severity: Minor
Summary: 
The "normative references" section states, "References to “VSIPL” or the
“VSIPL specification” refer to the VSIPL 1.1 API."  This needs to be
updated to 1.4.

Resolution: The references have been updated to refer to the canonical OMG URL. Changed item 1.2/3 (page 1) to: “References to “VSIPL” or the “VSIPL specification” refer to the VSIPL specification at http://www.omg.org/spec/VSIPL/”
Revised Text:
Actions taken:
October 23, 2012: received issue
April 1, 2013: closed issue

Issue 18214: Default value of Dense map type not described (vsiplxx-ftf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
Although the paragraphs describing the D, T, and O template parameters
for Dense<> mention the default value, the paragraph for M does not; it
should do so.

Resolution: Changed item 6.3.2/4 (page 32) to: “M must be a map type with a default constructor. Its default value is the Local_map type.”
Revised Text:
Actions taken:
October 23, 2012: received issue
April 1, 2013: closed issue

Issue 18257: Compliance section needed (vsiplxx-ftf)

Click here for this issue's archive.
Source: Object Management Group (Mr. Andrew Watson, andrew(at)omg.org)
Nature: Revision
Severity: Minor
Summary: 
There are three compliance points: the whole VSIPL specification, the Core profile (mars/12-02-07), and the Core lite profile (mars/12-02-08). All the information needed for a compliance section is present on page 1 (PDF page 23) and those two documents. If this specification had been written using the ISO/OMG document template, this is what it should contain. This is only a matter of presentation.

Resolution: On page 2, a new section 1.4 titled “Conformance” has been introduced following section 1.3 (“Functionality”), which includes what was previously the last paragraph of section 1.3.
Revised Text:
Actions taken:
November 13, 2012: received issue
April 1, 2013: closed issue

Issue 18258: Code examples in separate machine-readable file? (vsiplxx-ftf)

Click here for this issue's archive.
Source: Object Management Group (Mr. Andrew Watson, andrew(at)omg.org)
Nature: Revision
Severity: Minor
Summary: 
The code examples could usefully be provided as separate machine-readable files

Resolution: All example code is in fact now provided as separate C source files.
Revised Text:
Actions taken:
November 13, 2012: received issue
April 1, 2013: closed issue

Issue 18260: Numbered sections? (vsiplxx-ftf)

Click here for this issue's archive.
Source: Object Management Group (Mr. Andrew Watson, andrew(at)omg.org)
Nature: Revision
Severity: Minor
Summary: 
Sections should ideally be numbered. See ISO/OMG specification template

Resolution: The entire document has been reformatted after being transcribed from MS Word to DocBook. Sections are now properly numbered
Revised Text:
Actions taken:
November 13, 2012: received issue
April 1, 2013: closed issue

Issue 18262: Minor font issue (vsiplxx-ftf)

Click here for this issue's archive.
Source: Object Management Group (Mr. Andrew Watson, andrew(at)omg.org)
Nature: Revision
Severity: Minor
Summary: 
p31 (PDF page 53) There's a font formatting error. The words "Solve a covariance linear system" should be in Times not Courier font.

Resolution: Page 22, section 2.9.1.3: The above text has been properly reformatted as inline comment (/*...*/) embedded into (sample) code.
Revised Text:
Actions taken:
November 13, 2012: received issue
April 1, 2013: closed issue

Issue 18263: Another minor font issue (vsiplxx-ftf)

Click here for this issue's archive.
Source: Object Management Group (Mr. Andrew Watson, andrew(at)omg.org)
Nature: Revision
Severity: Minor
Summary: 
There are a few places where "VSIPL 1.0 compliance" is mentioned. This should presumably be "VSIPL 1.3 compliance" or "VSIPL 1.x compliance".

Resolution: Page 27, section 3.2.1, item “Functionality”: “VSIPL 1.0” has been changed to “VSIPL 1.4”. Likewise in Section 3.2.2, item “Arguments”.
Revised Text:
Actions taken:
November 13, 2012: received issue
April 1, 2013: closed issue

Issue 18266: Integrate addenda into main body of specification (vsiplxx-ftf)

Click here for this issue's archive.
Source: Mentor Graphics Corporation (Mr. Stefan Seefeld, stefan_seefeld(at)mentor.com)
Nature: Clarification
Severity: Minor
Summary: 
Three separate API additions have been added as "Addenda" to the original VSIPL spec:


1) VSIPL Interpolation API
2) VSIPL Permute API
3) VSIPL Sort API

Integrate all of those into the main structure of the specification.

Resolution: The “Addenda” sections have been fully integrated verbatim into the structure of the specification. They have become chapters 9 (“Interpolation”, page 478), 10 (“Permutation Functions”, page 492), and 11 (“Sort Functions”, page 501).
Revised Text:
Actions taken:
November 13, 2012: received issue
April 1, 2013: closed issue