Re: [VOTE] C++ standardize on return values only

2017-10-18 Thread Jacob Barrett
Stick with the out variable on this one and any others like this that are consistent with the Java API. The primary goal was to remove the very odd void readInt(int& int) calls. > On Oct 18, 2017, at 3:08 PM, Mark Hanson wrote: > > Sorry about that last email... to begin again > > Hello

Re: [VOTE] C++ standardize on return values only

2017-10-18 Thread Michael William Dodge
I have seen the uint8_t *, uint32_t tuple mostly with C-style system level calls (e.g., reading from a resource). Perhaps these could be allowed to remain as part of lowering impedance with a legacy API. Sarge > On 18 Oct, 2017, at 15:08, Mark Hanson wrote: > > Sorry about that last email...

Re: [VOTE] C++ standardize on return values only

2017-10-18 Thread Mark Hanson
Sorry about that last email... to begin again Hello All, So in doing some work on this subject, we have come across a case that David and I believed was worth raising for discussion. As one might expect, at some point, someone is going to pass in a buffer and a length into a function and

Re: [VOTE] C++ standardize on return values only

2017-10-18 Thread Jacob Barrett
> On Oct 18, 2017, at 2:49 PM, Mark Hanson wrote: > So in doing some work on this subject, we have come across a case that > David and I believed was worth raising for discussion. > > As one might expect, at some point, someone is going to pass in a buffer > and a length into a function and exp

Re: [VOTE] C++ standardize on return values only

2017-10-18 Thread Mark Hanson
Hello All, So in doing some work on this subject, we have come across a case that David and I believed was worth raising for discussion. As one might expect, at some point, someone is going to pass in a buffer and a length into a function and expect data put into that buffer, e.g. On Tue, Oct 3

Re: [VOTE] C++ standardize on return values only

2017-10-04 Thread Michael William Dodge
+1 for the tuple > On 4 Oct, 2017, at 08:01, Ernest Burghardt wrote: > > +1 Tuple > > On Wed, Oct 4, 2017 at 7:58 AM, David Kimura wrote: > >> +1 >> >> On Tue, Oct 3, 2017 at 5:45 PM, Hitesh Khamesra >> >> wrote: >> >>> Tuple option. >>> >>> Sent from Yahoo Mail on Android >>> >>> On Tue

Re: [VOTE] C++ standardize on return values only

2017-10-04 Thread Ernest Burghardt
+1 Tuple On Wed, Oct 4, 2017 at 7:58 AM, David Kimura wrote: > +1 > > On Tue, Oct 3, 2017 at 5:45 PM, Hitesh Khamesra > > wrote: > > > Tuple option. > > > > Sent from Yahoo Mail on Android > > > > On Tue, Oct 3, 2017 at 4:27 PM, Jacob Barrett > > wrote: Voting on the conversation around C++

Re: [VOTE] C++ standardize on return values only

2017-10-04 Thread David Kimura
+1 On Tue, Oct 3, 2017 at 5:45 PM, Hitesh Khamesra wrote: > Tuple option. > > Sent from Yahoo Mail on Android > > On Tue, Oct 3, 2017 at 4:27 PM, Jacob Barrett > wrote: Voting on the conversation around C++ return values vs. out > parameters. > This vote is to adopt the standard of return va

Re: [VOTE] C++ standardize on return values only

2017-10-03 Thread Hitesh Khamesra
Tuple option. Sent from Yahoo Mail on Android On Tue, Oct 3, 2017 at 4:27 PM, Jacob Barrett wrote: Voting on the conversation around C++ return values vs. out parameters. This vote is to adopt the standard of return values over the use of out parameters. On functions that must return more

[VOTE] C++ standardize on return values only

2017-10-03 Thread Jacob Barrett
Voting on the conversation around C++ return values vs. out parameters. This vote is to adopt the standard of return values over the use of out parameters. On functions that must return more than one value to use the C++11 std::tuple type for future compatibility with C++17. For example: std::tup