Return statement to exit code block early?

[johanatan]

Is there a 'return' statement to exit a code block early? I don't see any mention of it in the documentation and I haven't seen it used in any of the examples (though I haven't looked at each one).

Thanks.

[Justin]

Originally Posted by johanatan

Is there a 'return' statement to exit a code block early? I don't see any mention of it in the documentation and I haven't seen it used in any of the examples (though I haven't looked at each one).

Thanks.

Nope, no real plans for one either, but one might be pursuaded...

[johanatan]

Originally Posted by Justin

Nope, no real plans for one either, but one might be pursuaded...

Well, I think it would be nice because it would allow for saving a few clock ticks. For example, in my slicer code, you could say in the @block section to exit right away if the size of the block size is greater than the number of samples to drop per slice. This probably won't save too many ticks, but every little bit helps (and there may definitely be other situations where alot of ticks can be saved).

-Jonathan

[Justin]

Originally Posted by johanatan

Well, I think it would be nice because it would allow for saving a few clock ticks. For example, in my slicer code, you could say in the @block section to exit right away if the size of the block size is greater than the number of samples to drop per slice. This probably won't save too many ticks, but every little bit helps (and there may definitely be other situations where alot of ticks can be saved).

-Jonathan

of course doing

x < y ? (


);

would be approximately as fast. and the @block section only runs a few hundred times a second, typically...

[johanatan]

Originally Posted by Justin

of course doing

x < y ? (


);

would be approximately as fast. and the @block section only runs a few hundred times a second, typically...

Good point. Except it makes for an extra level of nesting. No biggie though I suppose.

I would like to do:

x < y ? return;

// other stuff

It would just keep the parenthesis matching a little easier for programmers/maintainers. Even a goto-label system would work, but then you could end up facilitating really intermingled code.

[cryptomail]

Another construct that could help with your early out (and also heavily debated within the annals of computing time ) , is the goto statement

Personally, I don't want to see it in there....but just bringing it up

IE:

loop:
variable ?
goto earlyout;

earlyout:
/* see ya */

Originally Posted by johanatan

Good point. Except it makes for an extra level of nesting. No biggie though I suppose.

I would like to do:

x < y ? return;

// other stuff

It would just keep the parenthesis matching a little easier for programmers/maintainers. Even a goto-label system would work, but then you could end up facilitating really intermingled code.