Anonymous user
Talk:Emirp primes: Difference between revisions
→reason for 3 invokes: (Gulp)!
(→reason for 3 invokes: not very good reason) |
(→reason for 3 invokes: (Gulp)!) |
||
Line 18:
:::: I wrote the C code, and you don't have to be so condescending, thank you very much. The C "commandline parsing" is an intentional joke, and silly it may be, there's nothing "hairy" about it. I chose not to parse the args, not because that requirement is difficult, but because it's stupid. Obviously you like commandline args, but there's no reason to make all your tasks "designed to use the command line", it only clutters and distracts. And not every language can be comfortably run with commandline args: Visual whatever language on Windows tend to get parameters from dialog boxes, JavaScript embedded in HTML don't get a commandline, PostScript don't get a commandline, and I'm sure there are more. You want to see how programs deal with different ranges, tell people to deal with different ranges, don't make silly commandments like "Invoke the (same) program once per task requirement". We don't all use REXX and in the way you use it, you know. --[[User:Ledrug|Ledrug]] ([[User talk:Ledrug|talk]]) 04:12, 25 March 2014 (UTC)
Hi Gerard, I too don't like the requirement of providing a command-line interface '''but''' I need to believe that there is a chance that me not wanting it parallels others not wanting to show program output which is something I have always found useful in making it easier to assess examples performance of the task.
So, (gulp), feel free to add an incomplete tag to the Python entry - it does not perform the task (which may well be reasonable to others such as yourself and you are the opposite of an RC newbie). --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 08:41, 25 March 2014 (UTC)
| |||