Timeline for "ComputedDate"'s interpretation of "next"
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 4, 2015 at 13:57 | history | edited | J. M.'s missing motivation | edited tags | |
| Apr 13, 2015 at 7:06 | answer | added | dr.blochwave | timeline score: 2 | |
| Nov 5, 2014 at 15:38 | comment | added | Hans | @mfvonh Have you tried "this" over "next". People have argued about definition of this Monday vs next Monday. Even Interpreter["ComputedDate"] /@ {"this Monday", "this Tuesday", "this Wednesday"} is ambiguous. Try "current". | |
| Nov 2, 2014 at 20:15 | comment | added | mfvonh | My bad, went over my head. Days Wednesday and forward are shifted shifted a week ahead as of today (Sunday). | |
| Nov 2, 2014 at 17:32 | comment | added | alancalvitti | I was joking, welcome to a new kind of speculative science. I don't think it's a TZ issue, try more days. | |
| Nov 2, 2014 at 15:27 | comment | added | mfvonh | That language obviously refers to the fact that the function can only recognize a finite number of patterns. There is only one type of pattern being submitted here and it is exhibiting inconsistent behavior; I did not say it was incorrect but rather asked if there was an explanation. Clearly "next" is a relative concept depending on when the week starts, so for all I know it is a timezone issue. | |
| Nov 2, 2014 at 5:31 | history | tweeted | twitter.com/#!/StackMma/status/528781517401501698 | ||
| Nov 2, 2014 at 1:23 | comment | added | alancalvitti | In all fairness, Interpreter documentation says "applied to a string to try to interpret..." What makes you believe its output should always be correct? | |
| Nov 1, 2014 at 22:28 | history | asked | mfvonh | CC BY-SA 3.0 |