Issue 18225: Vector destructor should call decrement_count (vsiplxx-rtf) Source: (Mr. Brooks Moses, brooks.moses(at)dpdx.net) Nature: Revision Severity: Minor Summary: The ~Vector() destructor function is described as "If this object is the only one using its block, the block is deleted. Otherwise, its block's use count is decremented by one." This is a redundant description of the decrement_block functionality, and further spreads the description of the block reference-counting throughout the standard. It would be much better to either (a) explicitly state that "This calls the block's decrement_count accessor, which may deallocate the block." Or, if we do not want to constrain the implementation to literally call the block method, we can alternately add a paragraph to the block requirements section describing increment-count and decrement-count functionality in general (with the increment_count and decrement_count functions being interfaces to it), and the ~Vector description should refer to that. 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: October 23, 2012: received issue Discussion: End of Annotations:===== te: Tue, 23 Oct 2012 14:03:42 -0700 From: Brooks Moses User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 To: Subject: VSIPL++ issue (#26 from me) X-OriginalArrivalTime: 23 Oct 2012 21:03:43.0048 (UTC) FILETIME=[E2507480:01CDB161] Name: Brooks Moses Employer: Mentor Graphics mailFrom: brooks_moses@mentor.com Terms_Agreement: I agree Specification: VSIPL++ Section: 8.2.3 [view.vector.constructors] FormalNumber: ptc/2012-07-27 Version: 1.2 - FTF Beta 1 Doc_Year: 2012 Doc_Month: August Doc_Day: 10 Page: 55 Title: Vector destructor should call decrement_count Nature: Bug Severity: Minor B1: Report Issue Description: The ~Vector() destructor function is described as "If this object is the only one using its block, the block is deleted. Otherwise, its block's use count is decremented by one." This is a redundant description of the decrement_block functionality, and further spreads the description of the block reference-counting throughout the standard. It would be much better to either (a) explicitly state that "This calls the block's decrement_count accessor, which may deallocate the block." Or, if we do not want to constrain the implementation to literally call the block method, we can alternately add a paragraph to the block requirements section describing increment-count and decrement-count functionality in general (with the increment_count and decrement_count functions being interfaces to it), and the ~Vector description should refer to that. - Brooks