Anonymous user
Talk:Execute a Markov algorithm: Difference between revisions
→Task addition
Line 169:
:::: Plus the fact that the ruleset definition includes a comment syntax (which I didn't write, just tidied up) is highly indicative that it was originally intended to be file-hosted. (I'm not sorry to lose the requirement for input and output data though.) –[[User:Dkf|Donal Fellows]] 09:37, 20 December 2009 (UTC)
:::::Hi Donal, on some operating systems, like flavours of Unix, stipluating the data source to be a file makes it very flexible, as most things are made to look like a file by the OS: ftp, HTTP, pipes, ... if your program aaccepts files, then all is well. This may not be the case in other operating systems. I think it is OK to treat the source of the data as a separate concern that is not part of the task. --[[User:Paddy3118|Paddy3118]] 23:12, 20 December 2009 (UTC)
:::The old Unix way would be to have a couple of flags -f rule_file, and optionally -o output_file. The input file would be any additional files specified on the command line or, if none were specified, from stdin. The output would be to stdout unles the -o option was specified.
:::examples:
::::process1 | markov -f myRules | process2
::::markov -f myRules -o myOut.txt myInput.txt myInput2.txt myInput3.txt
::::markov -f myRules < myInput.txt > myOutput.txt
:::--[[User:Rldrenth|Rldrenth]] 00:25, 21 December 2009 (UTC)
| |||