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 »
Q&A

Post History

50%
+0 −0
Q&A Tips for golfing in C

Abuse (as few) libraries (as possible) We don't want to use too much libraries when playing challenges. Sometimes, libraries aren't used at all in some answers in C. What if we want to shorten so...

posted 2y ago by General Sebast1an‭

Answer
#1: Initial revision by user avatar General Sebast1an‭ · 2021-08-08T08:46:00Z (over 2 years ago)
# Abuse (as few) libraries (as possible)

We don't want to use too much libraries when playing challenges. Sometimes, libraries aren't used at all in some answers in C.

What if we want to shorten some code? Functions do the trick, specifically built-ins. [It's specified you don't have to apply the byte count from accessing libraries](https://codegolf.codidact.com/posts/282802/282803#answer-282803), and with this in our advantage, we can use libraries, but it's better if we use only 1 or a few.