Nostr Web Client

I just released my first #OoT-inspired data structure: oot_bitset. it's so simple its a single header file in C with a few defines. Yes you heard it right. A datastructure library inspired by an n64 game from the 1998, thanks to the oot decompilation project. Now its documented and available for anyone to use.

It's almost so obvious in retrospect, but I don't think I've ever seen an implementation like this before. Usually its some complex library that tries to do everything. What if you only need to store less than 4096 flags compactly in a small array? This is the library for you.

Back in this era brutal simplicity was the norm. Sometimes I wish we got back to that.

https://github.com/jb55/oot_bitset

epsql 6mo ago

Very cool, how did you end discovering it? Were you just randomly exploring the repo?

Reply to this note

Please Login to reply.

Discussion

jb55 6mo ago

in the decompilation project, there is tons of code like this:

if (GET_INFTABLE(INFTABLE_TOLD_EPONA_IS_SCARED)) {

}

which led to these macros:

#define INFTABLE_INDEX(flag) ((flag) >> 4)

#define INFTABLE_MASK(flag) (1 << ((flag) & 0xF))

#define GET_INFTABLE(flag) (gSaveContext.save.info.infTable[INFTABLE_INDEX(flag)] & INFTABLE_MASK(flag))

#define SET_INFTABLE(flag) (gSaveContext.save.info.infTable[INFTABLE_INDEX(flag)] |= INFTABLE_MASK(flag))

#define CLEAR_INFTABLE(flag) (gSaveContext.save.info.infTable[INFTABLE_INDEX(flag)] &= ~INFTABLE_MASK(flag))

// INFTABLE 0x0-0xF

#define INFTABLE_INDEX_0 0

#define INFTABLE_00 0x00

#define INFTABLE_01 0x01

#define INFTABLE_03 0x03

#define INFTABLE_05 0x05

...

I was curious what the INDEX and MASK thing were doing and then I realized it was a bitset/bitvector/bitmap