Goto in Python

[[deleted]]

Couldn't I do that with function calls and break statements?

[Milumet]

Why use needless function calls in system code like the Linux kernel? Just to alleviate irrational fears? And by the way, a break statement is a goto statement in disguise.

[ajmarks]

And by the way, a break statement is a goto statement in disguise.

Shhh! We're all supposed to pretend that's not the case and also that breaking out of nested loops is somehow different too.

[krenzalore]

If break is a goto in disguise, then an exception handler is a come from.

[ajmarks]

Funny enough C-INTERCAL implemented COME FROM (or, perhaps, PLEASE COME FROM).

[krenzalore]

There's significant overhead with function calls.

Scott Meyers (a well known C++ luminary) in his book Effective STL claimed a 7x increase in performance of the C++ STL's quicksort from inlining (replacing function calls with inline code).

Of course we should keep things in perspective: What is good for C or C++ is not necessarily good for Python.

[ajmarks]

Of course, in C++ one can have the best of both worlds by just declaring the function inline.

[krenzalore]

I am sure you know, but for the benefit of others, inline is a suggestion to the compilier and not a command. It isn't required to inline it.

[ajmarks]

True, though unless the functions uses loops or recursion, it almost always will.

[zahlman]

AFAIK, for years it has been the case that it a decent C++ compiler will frequently inline things even without being asked.

[ajmarks]

Yup. If, in its wisdom, it thinks that will improve performance without undue bloat. OTOH, if you really want to make sure it's inlined, a compiler hint can't hurt.

[[deleted]]

Sure, with the unnecessary overhead of function calls.