check_cpu(3)

πŸ“¦ version 4.4.3.1, in fedora 43, fedora 44

✨ check_cpu(3) β€” the Allegro manual, but make it cute ✨

okay so we're in the Allegro manual, and today's main character is check_cpu. she's a lil function, she's lowkey iconic, and she has ONE job. let's get into it bestie 🫢


🌸 NAME 🌸

check_cpu β€” she detects the CPU type. πŸ’… Allegro game programming library, no cap.


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <allegro.h>

void check_cpu();

like. that's it. that's the whole vibe. void, no args, no return value, just pure aura ✨


πŸŽ€ DESCRIPTION πŸŽ€

So what does she actually do? check_cpu detects the CPU type and sets a bunch of global variables with whatever she finds out. πŸ”βœ¨

bestie listen: you don't normally need to call this yourself, because allegro_init() already does it for you. she's got you. let her cook. πŸ‘‘

it's giving "the intern who already did the task before you asked." obsessed. πŸ“


🌈 SEE ALSO 🌈

  • cpu_vendor(3) β€” who made your CPU, basically the birth certificate 🧚
  • cpu_family(3) β€” which family she belongs to, family tree energy πŸ’œ
  • cpu_model(3) β€” the specific model, her government name 😭
  • cpu_capabilities(3) β€” what she can actually do, the talent show πŸ”₯
  • allegro_init(3) β€” the one who calls check_cpu for you, the responsible friend πŸ™ˆ

and that's the whole page, bestie!! πŸ’– this was Allegro, version 4.4.3 β€” Allegro version 4.4.3, check_cpu(3), periodt. slay, stay compiled, and don't call functions that already called themselves βœ¨πŸ‘‘πŸ’…

πŸ“¦ where this page comes from