OvermindDL1 wrote:
Stewart, Robert wrote:
Beman Dawes wrote:
One particular concern is that as currently worded, the N2838 proposal requires throws() return a null reference, which they see [snip]
Why not have two functions of the same name, one takes a reference, the other a pointer, thus you can handle both cases and enforced that the reference cannot be null.
If you read the referenced proposal, you'll note that the idea was to avoid exploding interfaces to account for all functions using this error handling approach. That is, for every such function, there must be an additional overload, whereas a single overload suffices with the proposed design. _____ Rob Stewart robert.stewart@sig.com Software Engineer, Core Software using std::disclaimer; Susquehanna International Group, LLP http://www.sig.com IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.