View Single Post
Old 02 July 2020, 20:07   #6
Brick Nash
Registered User

Brick Nash's Avatar
Join Date: Mar 2015
Location: UK
Posts: 290
Originally Posted by roondar View Post
A different way of looking at this would be to split up the procedures into separate components. That saves the need for using goto's and is a good way to functionally split your program up into smaller components.

Such a method can help getting you smaller (sometimes even faster) and also easier to read/debug programs.

So, in this example you'd have Procedure 1, Procedure 2 and Procedure shared_1_2 (naming is for the example only, choose a name that fits what the procedures do )
Then, you'd call proc 1 or 2 and they'd call proc shared_1_2 as needed.
Yes I think that's the kind of thing I'm looking for. I love the fact that Procedures can be closed and compact to one line which is very tidy (I wish subroutines could do that), and I was trying to use them like subroutines but obviously they are a bit more detached than that.
Brick Nash is offline  
Page generated in 0.07539 seconds with 11 queries