SFC Practices: Jumps
Table of Contents
Introduction
Jumps often make SFCs hard to read and even harder to maintain, mostly they are a sign of developers' laziness. The use of jumps is strongly regulated so that even unfamiliar developers can quickly find their way around an SFC.
Downward Jumps
Downward jumps are generally not allowed, use branches instead. If it is not possible to use branches because they would cross, then the SFC must be restructured to make it work.
Upward Jumps
Only one upward jump is allowed per view (macro or SFC), the jump must be the last instruction on the view and must jump to the first step of the view, thus making loops possible. Because macros can be nested arbitrarily, it is also possible to display complex processes in a readable way.