Programming Megathread

Off Topic > Off Topic

<< < (12/241) > >>

ZSNO:

--- Quote from: Headcrab Zombie on October 29, 2015, 03:41:22 PM ---It's not like legacy systems or game dev are the only things to choose from. There's a ton of programming stuff out there

--- End quote ---
I was just trying to emphasize that there's a spectrum of types of programming jobs but there's good and bad things about all of them. c:

Otis Da HousKat:

--- Quote from: Foxscotch on October 29, 2015, 04:51:22 PM ---well, it has nothing to do with the exceptions
and you can always use pypy if you wanna be obsessive about speed

--- End quote ---
Not the way of handling exceptions solely, but the way Python likes to play it loose with interpreting and handling data at large.

Aide33:
So who's going into Software Engineering here?

I am and it's gonna be awesomeeeeeeee

I can't wait to go to uni

Headcrab Zombie:

--- Quote from: Foxscotch on October 29, 2015, 04:41:08 PM ---]in python that's the preferred way to do it

--- End quote ---
Catching exceptions is "preferred" when it prevents something from breaking
But catching exceptions when you can prevent them from being thrown in the first place is never preferred
And using exceptions as part of normal program flow is terrible because of the performance (as evident by the 100x speed increase when fixed) in c# (and python, too, according to this thread )

Foxscotch:
"When the usual case is no exception, try/catch is "extremely efficient" when compared to LBYL."
that's why it's better

I don't know how you could use a try/except block as part of normal flow, unless you're intentionally raising tons of exceptions where you don't need to. there's no reason for most normal things to raise exceptions, so you wouldn't even have an opportunity to catch anything

if you're going to want to do something like respond with a 400 error, you're gonna need to "check" it one way or the other, and try/except is better

Navigation

 Message Index

Go to full version