@@ -173,20 +173,26 @@ For a **physical** action, the preliminary time is similar, except that _t_ is r
173
173
174
174
If no ` <min_spacing> ` has been declared, then the tag of the event is simply the preliminary time
175
175
unless there is already an event scheduled for the same action with the same tag.
176
- In that case, a microstep is added to the tag.
177
- If there is again a previously scheduled event with the same tag, then a microstep is added to the tag again.
176
+ In that case, a microstep is added to the tag. If there is again a previously scheduled
177
+ event with the same tag, then a microstep is added to the tag again.
178
178
This process is repeated until there is no previously scheduled event with the same tag.
179
- This is equvalent to specifying a ` <min_spacing> ` of 0 with a ` "defer" ` policy.
180
179
181
180
If a ` <min_spacing> ` has been declared, then it gives a minimum logical time
182
- interval between the tags of two subsequently scheduled events. If the
181
+ interval between the tags of two subsequently scheduled events. The first effect this
182
+ has is that events will have monotically increasing tags. The difference between the
183
+ times of two successive tags is at least ` <min_spacing> ` . If the
183
184
preliminary time is closer than ` <min_spacing> ` to the time of the previously
184
185
scheduled event (if there is one), or if the preliminary time is earlier than
185
186
the previously scheduled event, then the time will be modified to enforce
186
187
the minimum spacing. The ` <policy> ` argument (if supported by the target)
187
188
determines how the minimum spacing constraint is enforced.
188
- Note that "previously scheduled" here means specifically the tag resulting from
189
- the most recent call to the schedule function for the same action.
189
+
190
+ Note that "previously scheduled" here means specifically the tag resulting from
191
+ the most recent call to the schedule function for the same action.
192
+
193
+ A ` <min_spacing> ` of 0 is not quite the same as no ` <min_spacing> ` declared.
194
+ With a ` <min_spacing> ` of 0, events will still have monotically increasing tags,
195
+ but the difference between the times of two successive tags can be 0.
190
196
191
197
<ShowIfs >
192
198
<ShowIf c py >
0 commit comments