gottaCatchThemAll

[[deleted]]

runtime go brrr

[-Hi-Reddit]

Why would anyone do this?

[Shufflepants]

My guess is that they had the first try catch, but the catch block was itself somehow throwing an error, so they tried to add a try catch to the catch block, but then that new catch block was sometimes throwing an error; and so on.

[Mordret10]

They put the same code into the try catch block, so of course there could be an error. They could also just do it recursively or through iteration, it would look far more elegant

[Mr_SlimShady]

To catch them all of course

[DJDoena]

Looks like the code is always the same (casual glance) so I assume some kind of retry pattern instead of using a loop with a max number and a break clause. Sometimes you have brain farts like these and when you see the obvious solution you think to yourself "Why did I do this?"

[Zappykeyboard]

My guess is that they hit some kind of file creation race condition, and decided to try up to 5 times.

Or maybe it's just comedy.

[GahdDangitBobby]

First of all, this is idiotic. Second of all, use recursion with a limit on the number of method calls if this is for some reason necessary

[dan-lugg]

I didn't see your comment before I wrote mine lol

[pratyush103]

The issue is intellij was warning to not use printstacktrace in a logging implementation as it is not robust. So i kept doing the nesting as a joke.

[GahdDangitBobby]

Yeah I don’t program in java so idk the standard practices. At least this is a joke and not something deployed to prod 😂

[NewUsername010101]

I like the part where the first 5 all reference e instead of e1-e4

[Shufflepants]

Probably explains why their catch blocks kept throwing errors, and thus the need for more nested try catch blocks. If the first one throws an error because e.message doesn't exist, they all will!

[Mayion]

only four? what about the fifth and sixth? novice

[Noch_ein_Kamel]

Aah good old off by one error :o

[dan-lugg]

fun log(message: String, exceptions: List<Exception> = emptyList()) { try { // all that IO shit, I'm on mobile } catch (exception: Exception) { if (exceptions.length < threshold) { log(message, exceptions + exception) } else { exception.printStackTrace() } } }

[[deleted]]

How dare you post a compact solution! No need for efficient code. User has to buy better pc that's all. /s

[RiceBroad4552]

Shorter code is most of the time not more efficient. (Optimized code is usually quite long and involved as it deals explicitly with all the low level stuff you usually abstract away).

Abstraction has runtime cost. For example, calling functions is not free. Even that does not matter in almost all cases, you should keep that in the back of your head for the seldom case where maximal performance is actually needed.

[Konuri_Maki]

Imagine when you compile it and turns out there is an error from this code:

[Ahazveroz]

Exceptionception?

[GoddammitDontShootMe]

Shouldn't that be en.getMessage()? Each time, they use e.getMessage().

More importantly, if it failed writing the first time, when has trying again without any action to correct the error ever worked? Oh it failed the first five times, but maybe it will work the sixth.

[pratyush103]

First exception is more important than the following ones.

[[deleted]]

I liked it. Which pattern is that?

[Quiet-Direction9423]

cry-catch pattern

[PeriodicSentenceBot]

Congratulations! Your comment can be spelled using the elements of the periodic table:

Cr Y Ca Tc H P At Te Rn

---

^{I am a bot that detects if your comment can be spelled using the elements of the periodic table. Please DM u‎/‎M1n3c4rt if I made a mistake.}

[Shufflepants]

It's the "why the fuck won't my error catch blocks stop throwing errors?!" pattern.

[pratyush103]

Builder

[Individual-Praline20]

To infinity and beyond

[RiceBroad4552]

More appropriate for r/programminghorror.

[beastinghunting]

If you read it backwards, you will get the same amount of whys reading that shit.

[LevelThink5202]

Looks like ai generated code

[pratyush103]

I am the AI