#WII DEVELOPERS PLEASE STAND UP
12 messages · Page 1 of 1 (latest)
I've been looking at the source code of existing projects.
How do you navigate/understand that source code?
That's more to do with like 20 years of coding experience--and no I don't understand it all, e.g. I haven't written a hardware driver before. I'm not really afraid to learn new things is another factor.
A lot of the homebrew code I've looked at also isn't exactly well-organized, but that people put effort into it and released it for other people to use is commendable--it just makes things take a bit longer to understand and interpret.
And it's not like anyone else was doing the same, so that's the best we've got for now. And when you're working mostly solo with no project management or anything, and especially if you're not getting paid, it's liable to end up a little disorganized, and that's okay.
Meanwhile, you're definitely going to need to gain some background in C/C++ as @zinc abyss mentioned. Lots of free resources available online to do that. I've been around enough programming languages that I'm fairly agnostic in terms of what language I use (except Perl, fuck Perl). Pointers and memory management are the biggest things that C/C++ requires understanding of compared to pretty much every other language meanwhile. E.g. "Rule of Three"
Scariest code I've ever looked at meanwhile was the pyc regular expression engine. It looks like someone built it off of a Turing machine model considering all the goto statements, but didn't include that in any documentation. Works, allows system interrupts where they need to be which can prevent reDOS attacks if a public interface is provided.
Man, how did perl get into here, quit dissing my camel homies
Honestly, I have no experience coding that much of anything other than a minecraft datapack, and that was with heavy tool assistance. The only coding language I really know relatively well is bash. BUT I did try testing my hand at making a homebrew application for the wii. It didn't work, but what I got out of it was that coding stuff for the wii was a lot like coding stuff for flash. It's understood very well, but there is no documentation on it. I wish you look, I wouldn't even know where to start