LabVIEW
Does labview have a "GO TO" function?
Google Translate:
... I am pressed for time and I need fast, accurate answers ...
The most concise answer is the link that for(imstuck) posted back in July 2011, linking to the state machine tutorial. The paper describes enums, shift registers, case structures, and loops.
I cannot think of a more accurate way to answer questions, than linking to reading material which has been peer-reviewed.
@TiTou wrote:
@smercurio_fc wrote:
Hmmm... I'm thinking something got lost in translation. I know I can get grumpy if my strawberry gets reduced.
Indeed!
Google actually softened the message a lot. I could give a translation but clearly there is no need for it.
I figured as much. Maybe I should have responded in Italian. There's a few Italian words I know that don't have "adequate" English transalations. 
@dav2010 wrote:
When I took Fortran in college many years ago, there was a feature where you could call a sub-routine by using this command "GO TO" and the complete syntax was something like "GO TO 100" and that would take you to line 100 and start executing line 100 and beyond (pardon me if I am not remembering it exactly correct).
The GOTO statement does not call a subroutine, it simply goes to a given statement in the same program. It is one of the few early statements that are considered harmful by many from a modern programming perspective.
This is pretty language independent and trying to translate it into LabVIEW obviously won't result is reasonable code there too. This is just my opinion. In a dataflow language, there are typically many hard data dependecies, so jumping to a different place in the code will typically not be able to keep dependencies intact and thus will not make a lot of sense.
If you feel that LabVIEW lacks a GOTO mechanism and really needs one, you could suggest it in the LabVIEW idea exchange. See how far it gets. Make sure to be very precise describing how it should look like and how it should function, as well as including some use cases. 😄
Not being able to identify code elements from a picture is a common forum problem (but typically not with basic primitives :o), that's why I typically insist that VIs or snippets be posted instead of images. Many primitives look similar (e.g. many array operations) and they can even change their design and shape depending on how they are wired. Thus you might see an icon that cannot be found (pixel by pixel) in the palettes at all. Having actual code makes it trivially easy: Just press ctrl+H for the context help and hover over the element in question. Easy as that!
I am happy you kept your quote in french to keep it in context of cultural stereotypes. 😄
Ctrl+H is your friend, the popup help and the linked descriptions basically makes all programming into included tutorial!
/Y
