Timeline for Are arrays -as data structures- suitable for constructors?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 23, 2017 at 19:37 | comment | added | Laiv | Somehow your answer alongside with JacquesB comments made me realise that I stated both my question here and my answer (there) under wrong assumptions. Sadly I can't check all the answers despite all of them are right. Thank you for the insights. | |
| Jul 22, 2017 at 10:53 | comment | added | Ewan | it doesn't. its "Just as a practical solution to thier unsolvable dilemma." | |
| Jul 22, 2017 at 10:13 | comment | added | Laiv | Ok. I buy you that :-). But how working with arrays solve the question around maintainability and scalability (OP's state that there're different messages so probably different "arrays"). | |
| Jul 22, 2017 at 10:02 | comment | added | Ewan | well at some point you have to map values to properties. I think the referred to question is basically 'how do i do this without doing that?' well, you can, but 'that' is the normal way of doing 'this' | |
| Jul 22, 2017 at 9:55 | comment | added | Laiv | Don't you think that encapsulating different concepts may do the thing easier? Even if it lead you to a hierarchy of classes? Otherwise, I don't see the point in OOP. | |
| Jul 22, 2017 at 9:51 | history | answered | Ewan | CC BY-SA 3.0 |