Talk:Halt and catch fire: Difference between revisions

From Rosetta Code
Content added Content deleted
(How general is this tasl?)
 
Line 1: Line 1:
== A bit limited ? ==
== A bit limited ? ==
Is this task to be taken literally - halt the CPU - and thus only be applicable only to the handful of assembly languages with samples already provided ?
Is this task to be taken literally - halt the CPU - and thus only be applicable to the handful of assembly languages with samples already provided ?
<br>Or does it mean "crash the program" by e.g. dividingh by zero or asserting a false condition or raising an unhandled exception or calling exit or...<br>
<br>Or does it mean "crash the program" by e.g. dividing by zero or asserting a false condition or raising an unhandled exception or calling exit or...<br><br>
Whilst reading about the fictitios HCF instruction was entertaining, do we want to encourage people to crash their CPUs ?<br>
Whilst reading about the fictitios HCF instruction was entertaining, do we want to encourage people to crash their CPUs ?<br><br>
--[[User:Tigerofdarkness|Tigerofdarkness]] ([[User talk:Tigerofdarkness|talk]]) 21:02, 12 September 2021 (UTC)
--[[User:Tigerofdarkness|Tigerofdarkness]] ([[User talk:Tigerofdarkness|talk]]) 21:02, 12 September 2021 (UTC)

Revision as of 21:05, 12 September 2021

A bit limited ?

Is this task to be taken literally - halt the CPU - and thus only be applicable to the handful of assembly languages with samples already provided ?
Or does it mean "crash the program" by e.g. dividing by zero or asserting a false condition or raising an unhandled exception or calling exit or...

Whilst reading about the fictitios HCF instruction was entertaining, do we want to encourage people to crash their CPUs ?

--Tigerofdarkness (talk) 21:02, 12 September 2021 (UTC)