Update to new [!NOTE] syntax

mandolaerik · mandolaerik · commit f6e0f6db213f · 2025-08-29T18:12:01.000+02:00
diff --git a/doc/1.2/language.md b/doc/1.2/language.md
@@ -569,13 +569,10 @@ inside the method must be enclosed in a `try` block. A `throw`
 statement counts as throwing, as does a `call` or `inline`
 statement, unless the method it invokes is declared `nothrow`.
 
-<div class="note">
-
-**Note:** In DML 1.4, `nothrow` is the default, and methods that
-*can* throw an exception must be explicitly declare that with
-a `throws` annotation.
-
-</div>
+> [!NOTE]
+> In DML 1.4, `nothrow` is the default, and methods that
+> *can* throw an exception must be explicitly declare that with
+> a `throws` annotation.
 
 ### Default Methods
 
diff --git a/doc/1.2/libraries.md b/doc/1.2/libraries.md
@@ -1348,13 +1348,9 @@ validate\_port(conf\_object\_t \*obj, const char \*port) -> (bool valid)
 Called before updating the value. If the return value is false,
 the attribute assignment will fail.
 
-<div class="note">
-
-**Note:** `validate` should be used instead, since `validate_port` is removed
-in DML 1.4.
-
-</div>
-
+> [!NOTE]
+> `validate` should be used instead, since `validate_port` is removed
+> in DML 1.4.
 
 </dd><dt>
 
diff --git a/doc/1.4/language.md b/doc/1.4/language.md
@@ -1332,23 +1332,21 @@ Also note that a parameter declaration without definition is redundant if a
 [typed parameter declaration](#typed-parameters) for that parameter already
 exists, as that already enforces that the parameter must be defined.
 
-<div class="note">
-
-**Note:** You may see the following special form in some standard library files:
-
-<pre>
-param <em>name</em> auto;
-</pre>
-
-for example,
-
-```
-param parent auto;
-```
-
-This is used to explicitly declare the built-in automatic parameters,
-and should never be used outside the libraries.
-</div>
+> [!NOTE]
+> You may see the following special form in some standard library files:
+>
+> <pre>
+> param <em>name</em> auto;
+> </pre>
+>
+> for example,
+>
+> ```
+> param parent auto;
+> ```
+>
+> This is used to explicitly declare the built-in automatic parameters,
+> and should never be used outside the libraries.
 
 ## Data types
 
@@ -1712,16 +1710,13 @@ handled:
 * A method can only be overridden by another method if it is declared
   `default`.
 
-<div class="note">
-
-**Note:** An overridable built-in method is defined by a template
-named as the object type. So, if you want to write a template that
-overrides the `read` method of a register, and want to make
-your implementation overridable, then your template must explicitly
-instantiate the `register` template using a statement `is
-register;`.
-
-</div>
+> [!NOTE]
+> An overridable built-in method is defined by a template
+> named as the object type. So, if you want to write a template that
+> overrides the `read` method of a register, and want to make
+> your implementation overridable, then your template must explicitly
+> instantiate the `register` template using a statement `is
+> register;`.
 
 ### Calling Methods
 
@@ -1911,12 +1906,9 @@ session struct_t s = { .y = { .i = 2, ... }, ... }
 Also unlike C, designator lists are not supported, and designated initializers
 for arrays are not supported.
 
-<div class="note">
-
-**Note:** Previously `session` variables were known as `data`
-variables.
-
-</div>
+> [!NOTE]
+> Previously `session` variables were known as `data`
+> variables.
 
 ## Saved variables
 
@@ -1970,14 +1962,11 @@ restricted to primitive data types, or structs or arrays containing
 only data types that could be saved. Such types are called
 [*serializable*](#serializable-types).
 
-<div class="note">
-
-**Note:** Saved variables are primarily intended for making checkpointable
-state easier. For configuration, `attribute` objects should
-be used instead. Additional data types for saved declarations are planned to
-be supported.
-
-</div>
+> [!NOTE]
+> Saved variables are primarily intended for making checkpointable
+> state easier. For configuration, `attribute` objects should
+> be used instead. Additional data types for saved declarations are planned to
+> be supported.
 
 ## Hook Declarations
 <pre>
@@ -2070,31 +2059,30 @@ arguments or return values. In fact, hook references are even
 Two hook references of the same hook reference type can be compared for
 equality, and are considered equal when they both reference the same hook.
 
-<div class="note">
-<b>Note:</b> Hooks have a notable shortcoming in their lack of configurability;
-for example, there is no way to configure a hook to log an error when a message
-is sent through the hook and there is no computation suspended on the hook to
-act upon the message. Proper hook configurability is planned to be added by the
-time or together with coroutines being introduced to DML. Until then, the
-suggested approach is to create wrappers around usages of <tt>send_now()</tt>.
-Hook reference types can be leveraged to cut down on the needed number of such
-wrappers, for example:
-<pre>
-method send_now_checked_no_data(hook() h) {
-    local uint64 resumed = h.send_now();
-    if (resumed == 0) {
-        log error: "Unhandled message to hook";
-    }
-}
-
-method send_now_checked_int(hook(int) h, int x) {
-    local uint64 resumed = h.send_now(x);
-    if (resumed == 0) {
-        log error: "Unhandled message to hook";
-    }
-}
-</pre>
-</div>
+> [!NOTE]
+> Hooks have a notable shortcoming in their lack of configurability;
+> for example, there is no way to configure a hook to log an error when a message
+> is sent through the hook and there is no computation suspended on the hook to
+> act upon the message. Proper hook configurability is planned to be added by the
+> time or together with coroutines being introduced to DML. Until then, the
+> suggested approach is to create wrappers around usages of <tt>send_now()</tt>.
+> Hook reference types can be leveraged to cut down on the needed number of such
+> wrappers, for example:
+> <pre>
+> method send_now_checked_no_data(hook() h) {
+>     local uint64 resumed = h.send_now();
+>     if (resumed == 0) {
+>         log error: "Unhandled message to hook";
+>     }
+> }
+>
+> method send_now_checked_int(hook(int) h, int x) {
+>     local uint64 resumed = h.send_now(x);
+>     if (resumed == 0) {
+>         log error: "Unhandled message to hook";
+>     }
+> }
+> </pre>
 
 ## Object Declarations
 
@@ -3504,13 +3492,10 @@ cancel all suspended method calls associated with an object through that
 object's `cancel_after()` method, as provided by the [`object`
 template](dml-builtins.html#object).
 
-<div class="note">
-
-**Note:** We plan to extend the `after` statement to allow for users to
-explicitly state what objects the suspended method call is to be associated
-with.
-
-</div>
+> [!NOTE]
+> We plan to extend the `after` statement to allow for users to
+> explicitly state what objects the suspended method call is to be associated
+> with.
 
 #### After Delay Statements
 <pre>
@@ -3913,13 +3898,10 @@ the selected case.
 DML currently only supports `#select` iteration on [compile-time list
 constants](#list-expressions).
 
-<div class="note">
-
-**Note:** The `select` statement has been temporarily removed from DML 1.4 due
-to semantic issues, and only the `#select` form may currently be used.
-The `select` statement will be reintroduced in the near future.
-
-</div>
+> [!NOTE]
+> The `select` statement has been temporarily removed from DML 1.4 due
+> to semantic issues, and only the `#select` form may currently be used.
+> The `select` statement will be reintroduced in the near future.
 
 ### #if and #else Statements
 <a id="if-else-statements"/>
diff --git a/doc/1.4/port-dml.md b/doc/1.4/port-dml.md
@@ -63,15 +63,14 @@ applied. The `port-dml` will detect this and emit a warning.
 You can choose to either port the code manually, or perform an analysis of
 an additional device that does use the code, and append that to the tagfile.
 
-<div class="note">
-
-**Note:** The `port-dml` script might fail because of a bug in the
-script. When this kind of bug is encountered, the script will normally
-print a traceback and point out a line in the tag file that it failed
-to apply; you can get further in your conversion by manually removing
-this line and re-running the script. After the script has succeeded,
-you can look up the failed tags in the [list of porting
-tags](changes-auto.html) and apply the change manually.
+> [!NOTE]
+> The `port-dml` script might fail because of a bug in the
+> script. When this kind of bug is encountered, the script will normally
+> print a traceback and point out a line in the tag file that it failed
+> to apply; you can get further in your conversion by manually removing
+> this line and re-running the script. After the script has succeeded,
+> you can look up the failed tags in the [list of porting
+> tags](changes-auto.html) and apply the change manually.
 
 </div>
 
diff --git a/lib/1.4/dml-builtins.dml b/lib/1.4/dml-builtins.dml
@@ -449,17 +449,14 @@ side-effects within `destroy()` such as logging will not be visible upon
 program exit unless deletion is explicitly performed beforehand &mdash; hence
 why `destroy` should *only* be used to ensure resources get cleaned up.
 
-<div class="note">
-
-**Note:** the `destroy` template can't be instantiated for
-`event` objects. This is because `event` objects, through the
-`custom_time_event` or `custom_cycle_event` template, may already require
-defining a method named `destroy` whose purpose is different from the one
-required by the `destroy` template. To work around this limitation, you may
-declare a `group` within the `event` object that instantiates the `destroy`
-template instead.
-
-</div>
+> [!NOTE]
+> the `destroy` template can't be instantiated for
+> `event` objects. This is because `event` objects, through the
+> `custom_time_event` or `custom_cycle_event` template, may already require
+> defining a method named `destroy` whose purpose is different from the one
+> required by the `destroy` template. To work around this limitation, you may
+> declare a `group` within the `event` object that instantiates the `destroy`
+> template instead.
 */
 template destroy {
     param _each_destroy : sequence(destroy);
@@ -1463,19 +1460,16 @@ a private helper object.
 The `init_as_subobj` template accepts one parameter,
 `classname`. This defines the class of the automatically created object.
 
-<div class="note">
-
-**Note:** The subobject class defined by the `classname` parameter is looked up
-using `SIM_get_class` while the module of the device class is being
-loaded.
-This may cause problems if the subobject class is defined within the
-same module as the device class:
-if the device class is defined before the subobject class, then the subobject
-class will not yet be defined, and the `SIM_get_class` call will fail.
-This problem can be resolved by moving the subobject class to
-a separate module.
-
-</div>
+> [!NOTE]
+> The subobject class defined by the `classname` parameter is looked up
+> using `SIM_get_class` while the module of the device class is being
+> loaded.
+> This may cause problems if the subobject class is defined within the
+> same module as the device class:
+> if the device class is defined before the subobject class, then the subobject
+> class will not yet be defined, and the `SIM_get_class` call will fail.
+> This problem can be resolved by moving the subobject class to
+> a separate module.
 
 The template also overrides the `configuration` parameter to
 `"none"` by default, which makes the connect invisible to the end-user.
