Talk:Instruction (computer science)

In the example, SHL is named operation (operator), shouldn't this be the same as opcode (and link to it) ?

Proposed merge of Instruction and Statement
Strong oppose Instructions and statements are completely different concepts. An instruction is an instruction-set architecture concept; a statement is a programming language concept. It would be a bad idea to try to treat them in the same article. You could argue that a "statement" in assembly language corresponds to an instruction, but even if it *corresponds*, it is not the same thing, and there are assembly language "statements" (not the usual term) which do not generate instructions at all. It would be a very bad idea to merge the two. --Macrakis 16:45, 20 February 2007 (UTC)

Also strong oppose, generally on the same grounds. It is rather common to contrast higher-level programming language constructs, including statements, and CPU / assembly language instructions in Computer Science / Programming texts, including many Wikipedia articles - usually in the contexts of inner loop optimization or portability.

I am going to remove the template suggesting the merger. --Yurakm 20:32, 16 March 2007 (UTC)