Peeny Cheez posted:

I avoid these issues by writing flawless, perferct code every time. I don't know why you guys haven't thought of it.

redleader posted:

thanks for the tip, professor of my graphics class

quote:

The key lesson, however, is that errors are values and the full power of the Go programming language is available for processing them.

Use the language to simplify your error handling.

But remember: Whatever you do, always check your errors!

Peeny Cheez posted:

I avoid these issues by writing flawless, perferct code every time. I don't know why you guys haven't thought of it.

Beamed posted:

I know this was posted in jest but this line of thought is just baffling to me, like sure okay let's pretend you actually write good code, let alone perfect code, there's -other poo poo your system is dealing with- that might cause errors you need to handle. ARGBHRWQHGEAHG

Beamed posted:

hardware issue, won'tfix

JawnV6 posted:

some place like the daily wtf had an interview horror story where the candidate was insisting that finally() blocks might not run and the interviewers were confident that one would always run

"what if I go up to the machine and unplug it? how does your finally() block run then?"
interviewers blanched, ended the interview

JawnV6 posted:

some place like the daily wtf had an interview horror story where the candidate was insisting that finally() blocks might not run and the interviewers were confident that one would always run

"what if I go up to the machine and unplug it? how does your finally() block run then?"
interviewers blanched, ended the interview

JawnV6 posted:

some place like the daily wtf had an interview horror story where the candidate was insisting that finally() blocks might not run and the interviewers were confident that one would always run

"what if I go up to the machine and unplug it? how does your finally() block run then?"
interviewers blanched, ended the interview

Peeny Cheez posted:

I avoid these issues by writing flawless, perferct code every time. I don't know why you guys haven't thought of it.

Peeny Cheez posted:

I avoid these issues by writing flawless, perferct code every time. I don't know why you guys haven't thought of it.

fart simpson posted:

our new department head unironically said that at his previous company they just got things right on the first try, and we should just do that too

Stringent posted:

i think the important distinction here would be is there any case where the finally() block would not run, but the rest of the program would. the answer to that should be no, but who the hell knows anything

fart simpson posted:

our new department head unironically said that at his previous company they just got things right on the first try, and we should just do that too

comedyblissoption posted:

throb pike

Peeny Cheez posted:

Stringent posted:

i think the important distinction here would be is there any case where the finally() block would not run, but the rest of the program would. the answer to that should be no, but who the hell knows anything

Internet Janitor posted:

i assume that the point of the exercise was to tease out something like

code:

public class DoOrDoNot {
	public static void main(String[] args) {
		try {
			System.out.println("YOSPOS");
			throw new Exception("wuh oh, not in amberpos.");
		}
		catch(Exception e) {
			Object b = new Object() {
				public void finalize() {
					System.out.println("I'M STILL KICKING, ASSHOLES.");
				}
			};
			Runtime.runFinalizersOnExit(true);
			System.out.println("BITHC!");
			System.exit(0);
			System.out.println("BITHC."); // this doesn't run.
		}
		finally {
			System.out.println("BITHC?"); // this also doesn't run.
		}
	}
}

code:

YOSPOS
BITHC!
I'M STILL KICKING, ASSHOLES.

Boiled Water posted:

I'm currently responsible for porting a piece of java code into python. I know no java.

it sure has a lot of @'s about

DONT THREAD ON ME posted:

don't worry, @ just means something magical is happening.

JawnV6 posted:

some place like the daily wtf had an interview horror story where the candidate was insisting that finally() blocks might not run and the interviewers were confident that one would always run

"what if I go up to the machine and unplug it? how does your finally() block run then?"
interviewers blanched, ended the interview

Peeny Cheez posted:

RetentionLevel.FUNTIME

jit bull transpile posted:

wish your posts were annotated @transient

jit bull transpile posted:

wish your posts were annotated @transient

Boiled Water posted:

I'm currently responsible for porting a piece of java code into python. I know no java.

it sure has a lot of @'s about

Suspicious Dish posted:

Why would you port something INTO pythong

Suspicious Dish posted:

Why would you port something INTO pythong