Timeline for Simple modern C++ string class implementation
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:24 | history | edited | CommunityBot |
Commonmark migration
|
|
| Sep 12, 2017 at 15:17 | comment | added | Matthieu M. | @cpp11dev: Two small clarifications. (1) I am not alluding to the PIMPL idiom, just proper layering of responsibilities instead of having one class doing it all. (2) You need not think about all requirements of all methods up-front, however I would suggest that each time you add a method you think about what you want it to do first, and if any change is necessary how that interacts with the requirements of the other methods (it's okay to change requirements, but this needs be a conscious choice). Ideally, changes of requirements should break tests, as those capture the requirements. | |
| Sep 12, 2017 at 14:30 | comment | added | cpp11dev | Amazing answer. And I really liked the approach you have suggested in tackling both the design and implementation. I believe, with your Impl design you are pointing towards PIMPL idiom. And your sentinel suggestion is what I had in my mind but could not implement it straight. Thank you for that. Appreciate your answer. So, by your suggestion, I should first design the class based on the requirements and then start my implementations, always. Cool | |
| Sep 11, 2017 at 14:50 | history | edited | Matthieu M. | CC BY-SA 3.0 |
added 181 characters in body
|
| Sep 11, 2017 at 14:44 | history | answered | Matthieu M. | CC BY-SA 3.0 |