Timeline for How we will find the source method
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2014 at 16:20 | comment | added | sfdcfox♦ | Namely, we can't access the stack, at least not directly. You have no idea how much I'd love to have access to the stack so we can figure out things like "how much more stack do I have before I have a stack overflow", etc. Instead, you just have to "know" where you are. In this simple case, it's easy, but I could imagine having a dozen entry points... | |
| May 28, 2014 at 15:53 | vote | accept | Noob_NoVoice | ||
| May 28, 2014 at 15:43 | answer | added | BarCotter | timeline score: 2 | |
| May 28, 2014 at 15:03 | answer | added | ManSpan | timeline score: 1 | |
| May 28, 2014 at 14:43 | comment | added | Keith C | Apex doesn't have any cool language features to help you do this. In you example, assuming when the constructors are used their arguments are not null, you can just check which of the lists is not null. | |
| May 28, 2014 at 14:40 | history | asked | Noob_NoVoice | CC BY-SA 3.0 |