piratepilates posted:

the evil fartbutt industrial complex

Notorious QIG posted:

triple sulk posted:

lol if u think this is as bad as it can get

LeftistMuslimObama posted:

is ipc inter-process communication? i didnt have to do that, but we did implement fork as well. this is everything i did for that course:
*implement fork and exec
*implement a bunch of other syscalls that escape me
*implement a ticket-based process scheduler
*implement a basic shell (really basic, really really basic, i wasn't allowed to use a parser library )
*implement a slab allocator
*change the virtual memory layout (the kernel we were using put the stack in the middle by default, we moved it to the top of the memory range and put the heap in the middle)
*implement spinlocks and semaphores
*implement an fsck tool for a super basic filesystem
*implement a few basic programs like cat and grep against a different filesystem
*implement multithreading

i was working full time throughout all my cs courses too, since epic was paying for them. i think i got like 2 hours of sleep a day max during that os course.

Eleeleth posted:

what's a good book if i wanna get less-terrible at database design?

Shaggar posted:

Just do it. If the design is good you will feel it.

fleshweasel posted:

yeah we're artists after all

more like dICK posted:

software fartistry

Finster Dexter posted:

lol ok

Eleeleth posted:

what's a good book if i wanna get less-terrible at database design?

Bloody posted:

lmao it turns out i am incredibly stupid. all i had to do to get current parser position is add a location <- getPosition line to my do blocks
now i have to refactor all of my data types to carry around their location i guess?

Shaggar posted:

when design is bad your autism will flare up and when it is good it will be soothed. you can get great pleasure from examining good data design.

Shaggar posted:

when design is bad your autism will flare up and when it is good it will be soothed. you can get great pleasure from examining good data design.

Luigi Thirty posted:

it's Friday and I don't feel like doing any work. I'm going to

homercles posted:

Did you have to implement all that stuff at the same time while leaping over alligators and fighting pirates? This is some super intense compsci undergrad course.

Bloody posted:

imagine you wanted to do some sort of series of operations in a sequential manner

here's some code snippets for doing that in verilog:

code:

integer current_state;
localparam state_idle = 0, state_fart = 1, state_butt = 2, state_fartbutt = 3, state_yospost = 4;

always @(posedge clock) begin // lol if you ever negedge clock
	case(currentstate)
	state_idle:
		// do nothing until we have some reason to
		if(do_a_thing == 1) current_state <= state_fart;
	end

	state_fart:
		do_a_fart <= 1; 
		butt_counter <= 13'd69; // verilog numeric literals are really good actually
		current_state <= state_butt;
	end

	state_butt:
		if (butt_counter == 0) begin
			current_state <= state_fartbutt;
		end else begin
			butt_counter <= butt_counter - 1;
		end
	end

	state_fartbutt:
		do_a_fart <= 0; // finally clear the fart-doing because are counter expired
		current_state <= state_idle;
	end
	endcase
end

Barnyard Protein posted:

yeah agreed, play with sqlite for a while, its good. Tcl is a lovely language in many regards but its OK for experimenting and messing around with sqlite.

if you know how to connect sqlite to mybatis in java, do that instead, then tell me how to do it because i can't get it to work with spring.

also i recommend the book "Using SQLite 3", its gives a good but high level view of database design and how to do selects and joins etc, it also is a good SQL reference.

Bloody posted:

i want to parse my source file into useful bits of data so that i can have things like "all of the variable declarations in this file" and then i want to look at that parsed output and say okay, you're actually redeclaring this identifier in two spots, here they are, or you declared this identifier on line 537 but never referenced it anywhere, or stuff like that. either the parsed objects know where they came from or i do multiple passes over the source

i don't want the parser to straight up fail the second time it encounters a declaration with a given identifier or anything i'd rather just parse as much as possible as permissively as possible then say "hey check out this stuff"

Bloody posted:

i want to parse my source file into useful bits of data so that i can have things like "all of the variable declarations in this file" and then i want to look at that parsed output and say okay, you're actually redeclaring this identifier in two spots, here they are, or you declared this identifier on line 537 but never referenced it anywhere, or stuff like that. either the parsed objects know where they came from or i do multiple passes over the source

i don't want the parser to straight up fail the second time it encounters a declaration with a given identifier or anything i'd rather just parse as much as possible as permissively as possible then say "hey check out this stuff"

JawnV6 posted:

you're too good, time to move on

wanna break intel chips? they're mad fun on the insides

HoboMan posted:

seriouspost: look up what 1st, 2nd, and 3rd normal form are. just knowing this you will be better than most "DBA"s out there

JawnV6 posted:

c'mon, fsm's aren't as scary as you're saying

and you should have a next_state register

VikingofRock posted:

Okay in that case what you are doing is completely reasonable. Carry on! Also post the code when you are done because this sounds neat.

Bloody posted:

they aren't scary but they are pointlessly verbose and the typical syntax for them is a cumbersome version of GOTO

Bloody posted:

ｄｅｎｏｒｍａｌｉｚｅ ｙｏｕｒｓｅｌｆ ａｎｄ ｆａｃｅ ｎｏｓｑｌ

Bloody posted:

ｄｅｎｏｒｍａｌｉｚｅ ｙｏｕｒｓｅｌｆ ａｎｄ ｆａｃｅ ｔｏ ｂｌｏｏｄｓｈｅｄ