stricter checks for RST headlines (#17089)
This commit is contained in:
parent
0fcf1af765
commit
d1fec552d0
9 changed files with 72 additions and 17 deletions
|
|
@ -77,7 +77,7 @@ the garbage collector with ``GC_enableMarkAndSweep`` and ``GC_disableMarkAndSwee
|
|||
|
||||
|
||||
Soft real-time support
|
||||
---------------------
|
||||
----------------------
|
||||
|
||||
To enable real-time support, the symbol `useRealtimeGC`:idx: needs to be
|
||||
defined via ``--define:useRealtimeGC`` (you can put this into your config
|
||||
|
|
|
|||
|
|
@ -183,7 +183,7 @@ Usually we just track the result of an expression: probably this should apply fo
|
|||
Also related to tracking initialization of expressions/fields.
|
||||
|
||||
unstructured control flow rules
|
||||
-------------------------
|
||||
-------------------------------
|
||||
|
||||
Unstructured control flow keywords as ``return``, ``break``, ``continue``, ``raise`` mean that we jump from a branch out.
|
||||
This means that if there is code after the finishing of the branch, it would be ran if one hasn't hit the direct parent branch of those: so it is similar to an ``else``. In those cases we should use the reverse nilabilities for the local to the condition expressions. E.g.
|
||||
|
|
|
|||
|
|
@ -154,7 +154,7 @@ but does nothing else. Here is an example of such a tree representation:
|
|||
|
||||
|
||||
Custom Semantic Checking
|
||||
-----------------------
|
||||
------------------------
|
||||
|
||||
The first thing that a macro should do with its arguments is to check
|
||||
if the argument is in the correct form. Not every type of wrong input
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue