提交: c20bcb7f8b322ca0290afe83f0f5df516c83cbd9 - DocIdeas (hg)

Commit MetaInfo

• 修订版: c20bcb7f8b322ca0290afe83f0f5df516c83cbd9 (tree)
• 时间: 2023-01-01 23:49:29
• 作者: Albert Mietus < albert AT mietus DOT nl >
• Commiter: Albert Mietus < albert AT mietus DOT nl >

Log Message

numbered Heisenbug-Blog

更改概述

• add: CCastle/4.Blog/a.Heisenbug.rst
• delete: CCastle/4.Blog/Heisenbug.rst

差异

diff -r 3a633eaba0a8 -r c20bcb7f8b32 CCastle/4.Blog/Heisenbug.rst
--- a/CCastle/4.Blog/Heisenbug.rst	Mon Dec 26 21:58:05 2022 +0100
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,43 +0,0 @@
-.. include:: /std/localtoc.irst
-
-.. _Castle-Heisenbug:
-
-======================
-Heisenbug (start/DRAF)
-======================
-
-
-.. post::
-   :category: CastleBlogs, Castle DesignStudy
-   :tags: Castle, DRAFT
-
-   In Castle, one can dynamically connect components and send “events” over those connections. Typically this is done as
-   an action on an incoming message (see: :ref:`CCC-Actors`). Depending on ‘:ref:`TheMachinery`’, those events can be
-   queued and result in a beautiful Heisenbug.
-
-   Before we give a simple example, let’s explain the Heisenbug first.
-   |BR|
-   Later, we continue with a generic solution (todo:-)
-
-
-What is e Heisenbug?
-=======================
-
-The heisenbug is named to Werner Heisenberg, who described the “observer effect”: when you look closely, the behavior
-changes. The same can happen to software (bugs). The behavior apparently changes when you study -or slightly adjust-
-that code.  Often this is due (small) changes in timing; possibly even in generated code. Therefore old (oldfashioned),
-sequential code on slow CPU’s is less likely to have heisenbugs then concurrent code on fast multi-core systems. It’s
-also common in threaded programs.
-
-The sieve goes wrong
---------------------
-
-Also my standard Caste demo ‘Sieve of Eratosthenes’ can suffer from this issue. The initial version did work for years,
-and failed horrible when another “machinery” was used.
-
-
-
-
- https://en.wikipedia.org/wiki/Heisenbug
-
-..  LocalWords:  heisenbugs, heisenbug

diff -r 3a633eaba0a8 -r c20bcb7f8b32 CCastle/4.Blog/a.Heisenbug.rst
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/CCastle/4.Blog/a.Heisenbug.rst	Sun Jan 01 15:49:29 2023 +0100
@@ -0,0 +1,43 @@
+.. include:: /std/localtoc.irst
+
+.. _Castle-Heisenbug:
+
+======================
+Heisenbug (start/DRAF)
+======================
+
+
+.. post::
+   :category: CastleBlogs, Castle DesignStudy
+   :tags: Castle, DRAFT
+
+   In Castle, one can dynamically connect components and send “events” over those connections. Typically this is done as
+   an action on an incoming message (see: :ref:`CCC-Actors`). Depending on ‘:ref:`TheMachinery`’, those events can be
+   queued and result in a beautiful Heisenbug.
+
+   Before we give a simple example, let’s explain the Heisenbug first.
+   |BR|
+   Later, we continue with a generic solution (todo:-)
+
+
+What is e Heisenbug?
+=======================
+
+The heisenbug is named to Werner Heisenberg, who described the “observer effect”: when you look closely, the behavior
+changes. The same can happen to software (bugs). The behavior apparently changes when you study -or slightly adjust-
+that code.  Often this is due (small) changes in timing; possibly even in generated code. Therefore old (oldfashioned),
+sequential code on slow CPU’s is less likely to have heisenbugs then concurrent code on fast multi-core systems. It’s
+also common in threaded programs.
+
+The sieve goes wrong
+--------------------
+
+Also my standard Caste demo ‘Sieve of Eratosthenes’ can suffer from this issue. The initial version did work for years,
+and failed horrible when another “machinery” was used.
+
+
+
+
+ https://en.wikipedia.org/wiki/Heisenbug
+
+..  LocalWords:  heisenbugs, heisenbug