It's UWAweek 47

help3002

This forum is provided to promote discussion amongst students enrolled in CITS3002 Computer Networks.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message. How do I ask a good question?

Displaying selected article
Showing 1 of 503 articles.
Currently 44 other people reading this forum.


 UWA week 18 (1st semester, week 9) ↓
SVG not supported

Login to reply

👍?
helpful
5:11pm Tue 30th Apr, ANONYMOUS

"Christopher McDonald" <ch*i*.*c*o*a*d@u*a*e*u*a*> wrote:
> Your question is not really about compilers, but about language standards or dialects: > https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gcc/Standards.html#C-Language > > If needing to use -std=gnu11, rather than just -std=c11 (gcc's current default is -std=gnu17) you must be selecting some additional features provided by GNU that may not, portably, be available in other environments. > > I'm interested to know what extra features your project requires, provided by -gnu11 but not standard C, > (as some other teams may benefit from them, too) ?
Well I've been going through A Guide to Network Programming using Internet sockets, by Brian "Beej" Hall, as suggested in the Getting Started section of the Project, and to use the getaddrinfo() function it is necessary to include the <netdb.h> header file. After doing some research, "Adding std=c11 undefines __USE_POSIX macro which guards addrinfo struct in netdb.h" ( where addrinfo is a struct used by getaddrinfo() ). I'm not sure if it is unnecessary for me to be using getaddrinfo() in the first place, but I'm just curious to know whether we are meant to be sticking with the -std=c11 flag

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy