You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be called an oversight, but the if and setup_proc are configured to be immediate execution commands. This means if they are entered interactively, they will execute immediately even if there is a time block on the operator command stream. This is not an issue for the schedule stream, which doesn't have the functionality of immediate execution commands. So it is benign in schedules.
These commands should probably be changed to be "normal" commands, but maybe there should be some reflection on whether that might cut-off some desired functionality.
I would note in passing that the break command has been disabled and that contrary to the intended design, it is possible to force immediate execution of a procedure (proc@!) during a time block. Will think about fixing those.
The text was updated successfully, but these errors were encountered:
I think it would be called an oversight, but the
if
andsetup_proc
are configured to be immediate execution commands. This means if they are entered interactively, they will execute immediately even if there is a time block on the operator command stream. This is not an issue for the schedule stream, which doesn't have the functionality of immediate execution commands. So it is benign in schedules.These commands should probably be changed to be "normal" commands, but maybe there should be some reflection on whether that might cut-off some desired functionality.
I would note in passing that the
break
command has been disabled and that contrary to the intended design, it is possible to force immediate execution of a procedure (proc@!
) during a time block. Will think about fixing those.The text was updated successfully, but these errors were encountered: