alex/gba
1
0
Fork 0
mirror of https://github.com/italicsjenga/gba.git synced 2025-01-11 19:41:30 +11:00
Code Issues Packages Projects Releases Wiki Activity

the old sentence didn't

Browse source
This commit is contained in:
Lokathor 2018-12-10 10:21:18 -07:00
parent f390f19c29
commit 578a00fffd
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
book/src/00-introduction/06-help_and_resources.md
View file

@ -45,7 +45,9 @@ We have personally used some or all of the following:
* [TONC](https://www.coranac.com/tonc/text/): While GBATEK is basically just a * [TONC](https://www.coranac.com/tonc/text/): While GBATEK is basically just a
huge tech specification, TONC is an actual _guide_ on how to make sense of the huge tech specification, TONC is an actual _guide_ on how to make sense of the
GBA's abilities and organize it into a game. It's written for C of course, but GBA's abilities and organize it into a game. It's written for C of course, but
it's a large as a Rust programmer you should always be practicing your ability to read C
code anyway. It's the programming equivalent of learning Latin because all the
old academic books are written in Latin.
* [CowBite](https://www.cs.rit.edu/~tjh8300/CowBite/CowBiteSpec.htm): This is * [CowBite](https://www.cs.rit.edu/~tjh8300/CowBite/CowBiteSpec.htm): This is
more like GBATEK, and it's less complete, but it mixes in a little more more like GBATEK, and it's less complete, but it mixes in a little more
friendly explanation of things in between the hardware spec parts. friendly explanation of things in between the hardware spec parts.