Timeline for Topicality of question "Project Euler #52 - Permuted multiples"
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 15, 2015 at 17:23 | vote | accept | Dan | ||
| Jul 12, 2015 at 15:33 | vote | accept | Dan | ||
| Jul 12, 2015 at 15:33 | |||||
| Jul 12, 2015 at 14:30 | comment | added | nhgrif | I'm not commenting on how you should answer. I added some comments about iOS, which I'm more familiar with. If today someone posted some ancient form of Objective-C that would compile in Xcode 3, but wouldn't compile in Xcode 6.4 or Xcode 7, I wouldn't be voting to close the question as broken (unless I felt like finding a version of Xcode 3 and prove it was broken there), but I also wouldn't feel the urge to answer an outdated and ultimately irrelevant question. Just because the question isn't off-topic doesn't mean it's worth answering. | |
| Jul 12, 2015 at 14:28 | history | edited | nhgrif | CC BY-SA 3.0 |
added 740 characters in body
|
| Jul 12, 2015 at 14:27 | comment | added | Dan | I would agree that if OP absolutely has to only support SpiderMonkey 1.8.5 (or whatever else), then it is working code. However, his post states no such requirement - it's a project Euler question - and it's syntactically incorrect JavaScript as per the ES5 specification. The only reason it would ever work is by a bug or incorrect implementation of the ES5 specification. Would the appropriate course of action be to review the code but leave a warning indicating that the code would not be invalid in other environments (such as Chrome, both NodeJS/IoJS and possibly Chakra)? | |
| Jul 12, 2015 at 14:24 | history | answered | nhgrif | CC BY-SA 3.0 |