Timeline for non-optional pointers vs. non-const references in C++
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 5, 2015 at 11:32 | history | edited | Caleth | CC BY-SA 3.0 | added 28 characters in body |
| Oct 5, 2015 at 11:31 | comment | added | Caleth | Yes, avoid output parameters, prefer composite return types, edited to make that clearer | |
| Oct 5, 2015 at 10:20 | comment | added | Wolf | You mean, the only place where I'm not able to provide a non-mandatory pointer? True, but I'm not sure if your rule The only place where... is really applicable to all cases. What you suggest looks like: avoid output parameters in the functions of your own programs. True for new programs. | |
| Oct 5, 2015 at 10:09 | history | answered | Caleth | CC BY-SA 3.0 |