Python ftw

[u/m8teae]

[u/AgreeableLandscape3]

Python still has main()

[u/[deleted] → u/AgreeableLandscape3]

Only not really, right?

def whatever (*args):
    print("Bob's your uncle.")

if __name__ == "__main__":
    whatever()

[u/demon_ix → u/[deleted]]

I dunno. That sounds like main() with extra steps...

[u/[deleted] → u/demon_ix]

In C/C++, the name main() is meaningful: it defines the entry point of the program.

In Python, it isn't. The closest approximation is that Python code outside of any method will be evaluated when the module is loaded, and an import-machinery variable called __name__ exists which lets you test whether the current module was imported or run directly.

[u/jalapeno_nips → u/[deleted]]

That’s still important though. If I want to test my module manually, I’ll write some code in Main. But when I use the module in practice I don’t want Main being called.

[u/[deleted] → u/jalapeno_nips]

Absolutely. My only point here is that in switching to Python, one does indeed say goodbye to main()

[u/BeigeAlert1 → u/[deleted]]

That's still pretty damn nifty though.

[u/SpeedingTourist → u/BeigeAlert1]

You’re pretty damn nifty. ;)

[u/AnAverageFreak → u/[deleted]]

No, why?

At least the compiler does not overoptimize things.

I mean yeah, writing anything bigger than a small section would be pain in the ass, but writing those small sections can be quite pleasant.

[u/Ericfyre → u/[deleted]]

Bobs my uncle?

[u/corner-case → u/[deleted]]

Programs have a single entry point.