I'm curious if the order which #include statements are offered in man pages are important.
For example, man 3 inet_addr has the following #includes:
#include <sys/socket.h>
#include <netinet/in.h>
#include <arpa/inet.h>
Does it break anything to change the order to:
#include <arpa/inet.h>
#include <netinet/in.h>
#include <sys/socket.h>
? It's mostly an OCD thing, but being able to would help my brain.
I don't know about these particular ones, but historically there have been cases of libraries with finnicky headers requiring a particular order of inclusion. Best practice is to make headers self-contained such that the order doesn't matter, and you should find that to be the case here.
Look up a C++ Reference and learn How To Ask Questions The Smart WayOriginally Posted by Bjarne Stroustrup (2000-10-14)
Ty for your response.
But if there is a problem, will it show during compile time? Or is it a case where you'd have to fully test the program to be sure?
The problems will normally happening during Compile time.
Edit: I have never had one happen during run-time; I think I can remember one happening during linking.
Tim S.
Last edited by stahta01; 04-23-2020 at 09:30 AM.
"...a computer is a stupid machine with the ability to do incredibly smart things, while computer programmers are smart people with the ability to do incredibly stupid things. They are,in short, a perfect match.." Bill Bryson
