Talk:Terminal control: Difference between revisions
Content added Content deleted
(Task?) |
(→Terminals?: new section) |
||
| Line 2: | Line 2: | ||
==Is this a task, really?== |
==Is this a task, really?== |
||
How can this be a task if it has no goals to achieve in it? Perhaps it should be converted into a category? –[[User:Dkf|Donal Fellows]] 12:14, 8 October 2010 (UTC) |
How can this be a task if it has no goals to achieve in it? Perhaps it should be converted into a category? –[[User:Dkf|Donal Fellows]] 12:14, 8 October 2010 (UTC) |
||
== Terminals? == |
|||
The concept of "what is a terminal" has some ambiguities. |
|||
For example, some languages, which interact only with a single class of hardware, have a much simpler job than other languages which deal with a wide variety of hardware. |
|||
Consider, for example, |
|||
# a language which interacts with a browser (like javascript), |
|||
# a language which runs only on certain hardware (like some dialects of basic), |
|||
# a language which uses some specialized graphical environment (like logo), |
|||
# a language which probably can assume unix is present (like awk), |
|||
# a language in typical use might have to deal with any of the above cases, or others... (like java) |
|||
Perhaps these tasks could do with an explicit statement that any kind of terminal control is acceptable? |
|||
--[[User:Rdm|Rdm]] 19:16, 15 October 2010 (UTC) |
|||
Revision as of 19:16, 15 October 2010
Note that terminals have a "bell" even if it's implemented as a beep. Let's use the correct terminology. –Donal Fellows 08:48, 5 October 2010 (UTC)
Is this a task, really?
How can this be a task if it has no goals to achieve in it? Perhaps it should be converted into a category? –Donal Fellows 12:14, 8 October 2010 (UTC)
Terminals?
The concept of "what is a terminal" has some ambiguities.
For example, some languages, which interact only with a single class of hardware, have a much simpler job than other languages which deal with a wide variety of hardware.
Consider, for example,
- a language which interacts with a browser (like javascript),
- a language which runs only on certain hardware (like some dialects of basic),
- a language which uses some specialized graphical environment (like logo),
- a language which probably can assume unix is present (like awk),
- a language in typical use might have to deal with any of the above cases, or others... (like java)
Perhaps these tasks could do with an explicit statement that any kind of terminal control is acceptable?
--Rdm 19:16, 15 October 2010 (UTC)