Timeline for Instantiating a property when the required attributes have been set
Current License: CC BY-SA 3.0
14 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 3, 2016 at 1:45 | answer | added | Tolani | timeline score: 1 | |
Jul 2, 2016 at 11:03 | vote | accept | STORM | ||
Jul 1, 2016 at 21:39 | history | edited | Tunaki | CC BY-SA 3.0 |
deleted 5 characters in body; edited tags
|
Jul 1, 2016 at 21:37 | history | edited | 200_success | CC BY-SA 3.0 |
deleted 17 characters in body; edited tags; edited title
|
Jul 1, 2016 at 21:03 | answer | added | I'll add comments tomorrow | timeline score: 1 | |
Jul 1, 2016 at 19:08 | answer | added | t3chb0t | timeline score: 1 | |
Jul 1, 2016 at 18:57 | review | Close votes | |||
Jul 1, 2016 at 21:39 | |||||
Jul 1, 2016 at 18:56 | comment | added | t3chb0t | I looks much better now then the I-have-no-idea-how-to-program code before ;-) | |
Jul 1, 2016 at 18:52 | comment | added | STORM | I have changed it. But i have currently no final code, i am only working on a concept. | |
Jul 1, 2016 at 18:51 | history | edited | STORM | CC BY-SA 3.0 |
deleted 620 characters in body
|
Jul 1, 2016 at 18:47 | history | edited | Pimgd | CC BY-SA 3.0 |
added 1 character in body
|
Jul 1, 2016 at 18:47 | comment | added | Pimgd | "Lets assume that we have a simple class with multiple properties" -> Close vote - hypothetical code. Here at Code Review we prefer concrete working code, not hypothetical examples, as there is no definitive answer for hypotheticals. | |
Jul 1, 2016 at 18:38 | comment | added | forsvarir |
Because this isn't real code, it's really hard to figure out what you're doing and why. If you need to obfuscate your code, try to come up with a meaningful solution that mirrors the behaviour you're talking about in a realistic way. For example this, assign a to b is unlikely to occur in your real solution in such an abstract way: this.ClassB = a
|
|
Jul 1, 2016 at 18:28 | history | asked | STORM | CC BY-SA 3.0 |