Timeline for Bizarre behavior of With, Compile and Break
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 18, 2014 at 14:18 | vote | accept | Pillsy | ||
| Apr 17, 2014 at 22:12 | comment | added | Leonid Shifrin | @OleksandrR. Thanks, good to hear! Particularly from you, given that you have an extensive knowledge of Compile -related matters. I'd be interested to dig deeper myself, but I never have the time for it. | |
| Apr 17, 2014 at 22:04 | comment | added | Oleksandr R. | Very good, +1 of course! Incidentally it would also be acceptable to put ++i; Null rather than Break[]; 0. Your analysis is correct either way. | |
| Apr 17, 2014 at 21:40 | comment | added | Leonid Shifrin | @halirutan I can't agree more! | |
| Apr 17, 2014 at 21:38 | comment | added | halirutan | +1 This issue is as awful as the type annotation with something like i=Most[{0}] inside Compile. Sometimes it would be better to cry difficulties out loud and document them instead of being silent and let users run onto ground. | |
| Apr 17, 2014 at 21:20 | history | answered | Leonid Shifrin | CC BY-SA 3.0 |