Anonymous user
Talk:Interactive programming (repl): Difference between revisions
Talk:Interactive programming (repl) (view source)
Revision as of 21:02, 12 April 2009
, 15 years agoCLI or line editor
(CLI or line editor) |
|||
Line 51:
If an interpreted language is by design able to read the standard input and to interpret it, this is considered like a "command line interpreter", or is just a side effect...? ... E.g. "<tt>awk -f -</tt>" starts AWK reading the source from standard input... and when the input is "finished", it ''executes'' the code... it seems like command line interpretation... can it be considered so? --[[User:ShinTakezou|ShinTakezou]] 23:00, 11 April 2009 (UTC)
:I don't think Awk has a CLI. I would draw the line here and look for a bit more support from the language. Perl's use of its debugger I think would qualify, but both Perl and Python could be called in such a way that they read their program file from standard input. Merely using pseudo-files and/or redirection to enable compilers/interpreters to use standard input in place of a program file name should not be taken, in this task, to be using a CLI. --[[User:Paddy3118|Paddy3118]] 10:24, 12 April 2009 (UTC)
== CLI or line editor ==
I don't quite understand this task. First it talks about command line interpreter, and then requires creating a function. Command line interpreters do not create functions, they interpret and execute commands. If you are creating a function into a program, you are using an editor. For example, a traditional Basic interpreter uses a command mode which also acts as line editor. You can enter a direct command, and it is executed when you press enter. But if you precede the command with a line number, it is entered as a line in the program. In that case, you are using the editor. --[[User:PauliKL|PauliKL]] 21:02, 12 April 2009 (UTC)
| |||