Sorry your browser is not supported!

I've been moving parts of my code into functions, and I've recently put a piece of code and the gosubs it calls into a function. Suddenly my code would just end after calling the function, not giving any error, but just ending the program. It was as if the function was not returning to where I'd called it from. After some testing, I found out that this only happened when there were gosub subroutines in the function, regardless of whether I was calling them or not.

Can I not put subroutines in a function, seeing as it is something of a subroutine itself? That would be awful, I think, as I want to eventually export this function to and #include file, and it would be much harder to deal with without subroutines.

I can't imagine that working, as subs and functions are fundamentally different in how they are used in the program. They both have a similar, but mutually exclusive scope. (You cannot have a function in a sub, either.)

Actually, a subroutine is more like a function that accepts no parameters and returns no value. Functions create call instructions, and use the stack. Subroutines create call instructions , but do not use the stack beyond pushing a return address on there.

No worries, I do that all the time. You anticipate scope problems, but there are none. Most folks prefer subs because they are not aware that functions do not have to have scope problems at all. you just have to get better at data management when using functions that operate on global variables.

So, you will probably have to learn how to manage your variables yourself to make it work, but that's not a bad thing, really.

As functions and subroutines 'return' to where they were called automatically, they have to store this information. For this, the stack is used.

Bear in mind that when you go into a function, DB assumes that the value it puts on the stack is going to required at the end of that function and putting a procedure in the middle can corrupt the stack - sending the program counter to the wrong part of the program, crashing it.

TDK_Man

have you tried keeping all the subs inside the function like a mini program.
I haven't tried it but could work.