Conversation

Notices

1. Embed this notice
   opal hart (opal@ap.maladaptive.art)'s status on Sunday, 16-Oct-2022 13:24:33 JST opal hart
   wonder why nobody #includes .c files much just to make single units of code easier to look at
   • Embed this notice
     spiral@anime.website's status on Sunday, 16-Oct-2022 13:28:37 JST spiral

     in reply to
     @opal i've done that in the past with C, maybe because i'm used to languages that don't use header files
     opal hart likes this.
   • Embed this notice
     opal hart (opal@ap.maladaptive.art)'s status on Sunday, 16-Oct-2022 13:31:02 JST opal hart

     in reply to

     • djsumdog
     @djsumdog you can use `#pragma once` instead of ifdef guards, it's well-supported on most compilers. anyway that's up to you, the only real reason to even guard header files is to avoid recursive dependencies by headers that indiscriminately include other stuff
   • Embed this notice
     djsumdog (djsumdog@djsumdog.com)'s status on Sunday, 16-Oct-2022 13:31:03 JST djsumdog

     in reply to
     huh ... I never even thought about doing that. Buy would each .c file need the same `#ifndef/#define/#endif` that headers files normally need so they don't get included twice?