I understand what halting is, i am just saying that a clarification, like the above, would make other people more prone to participate in the discussion.
how about an algorithm that first takes note of the condition under which a particular event is supposed to halt.
notes the conditions under which any explicit brakes in the particular process will occur, and what variables will effect those conditions.
steps through the decision process a couple of times, to see how the variables that effect the exit conditions are changed.
finally determines if any of the conditions that cause the algorithm to exit will ever exist.
sounds like some self-modifying code actually to be smart enough to create a child that will monitor the explicit loop conditions...
----------------
Microsoft, the leader in using innovative tactics to promote irksome experience, coupled with antiquated technology that's held together by a pyramid of makeshift afterthoughts.
Apple, the leader in using irksome tactics to promote innovative experience, coupled with an antiquated core that's enhanced by state-of-the-art afterthoughts.
Linux, the leader in not using any tactics to promote user-defined experience, coupled with state-of-the-art core enhanced by innovative afterthoughts.
