Issue 16404: Improving usability of EntityQoS API (dds-psm-cxx-ftf) Source: Real-Time Innovations (Dr. Sumant Tambe, sumant(at)rti.com) Nature: Clarification Severity: Minor Summary: 8. Supporting method chaining for setting qos parameters would improve readability of the API. For instance, DataWriterQos dwqos; dw >> dwqos; Dwqos.policy<History>().kind(KEEP_ALL).depth(200); Dwqos.policy<ResourceLimits>().max_samples(p).max_instances(q).max_samples_per_instance(r); dw << dwqos; Currently, it needs different function calls for every qos parameter. Proposed Solution: Change all the normative core qos policy classes (e.g., History, ResourceLimits) to return a reference to itself from the setters. Currently they return nothing. Resolution: Revised Text: Actions taken: July 29, 2011: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 29 Jul 2011 20:35:15 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Sumant Tambe Employer: Real-Time Innovations mailFrom: sumant@rti.com Terms_Agreement: I agree Specification: DDS C++ PSM Section: 7 FormalNumber: ptc/2011-01-02 Version: Beta 1 Doc_Year: 2011 Doc_Month: January Doc_Day: 02 Page: 4 Title: Improving usability of EntityQoS API Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Description: 8. Supporting method chaining for setting qos parameters would improve readability of the API. For instance, DataWriterQos dwqos; dw >> dwqos; Dwqos.policy().kind(KEEP_ALL).depth(200); Dwqos.policy().max_samples(p).max_instances(q).max_samples_per_instance(r); dw << dwqos; Currently, it needs different function calls for every qos parameter. Proposed Solution: Change all the normative core qos policy classes (e.g., History, ResourceLimits) to return a reference to itself from the setters. Currently they return nothing.