@altenbach wrote:
@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. 😄
Just to clarify: The question about GOTO was from a year ago. This crovax39 added a post 1 year, 3 days later asking to identify what was an enum. He then followed up asking to identify what a case structure was. So, the rest of the posts were about this whole "identify these very basic items from LabVIEW for me".
