Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

Approved.
This suggested edit was approved and applied to the post 10 months ago by Monica Cellio‭.

11 / 255
  • There is basically only one reason not to use static functions in C, as apposed to functions with global scope. That's if you want to access the function from outside the module.
  • Otherwise, if the function is only used in the specific module, then it's beneficial to not export it to the whole world. By making is <tt>static</tt> (a bad name for not global, but that's C) you know that the only callers to the function are local to the module.
  • It also means the function is only in the namespace of the module, and you don't have to worry about being unique within the global scope. For example multiple modules can have local functions called <tt>init_state</tt> without any problems.
  • So overall, the answer is to make functions <tt>static</tt> in C unless they are meant to be called from outside the module.
  • There is basically only one reason not to use static functions in C, as opposed to functions with global scope. That's if you want to access the function from outside the module.
  • Otherwise, if the function is only used in the specific module, then it's beneficial to not export it to the whole world. By making it <tt>static</tt> (a bad name for "not global", but that's C) you know that the only callers to the function are local to the module.
  • It also means the function is only in the namespace of the module, and you don't have to worry about being unique within the global scope. For example multiple modules can have local functions called <tt>init_state</tt> without any problems.
  • So overall, the answer is to make functions <tt>static</tt> in C unless they are meant to be called from outside the module.

Suggested 10 months ago by Lover of Structure‭