This program was created and tested on Mac os x darwin
The main focus on this project is static variables, buffering output and some of the basics of file descriptor's
While this function is very useful in it's own right I'm coming to find that it's the core concept that I end up using more then the actual function. Being able to wait for a line of input from the user is a common task in programming.
get_next_line makes that easy by abstracting the task away, but there are some instances where it may not be as useful, mainly; What happens when I need to proccess input that does not contain a newline example (ctrl-C, arrow keys, etc..)? In those cases the core functionality here provides everything you need to be able to copy/paste and modify everything as needed.
The get_next_line function is buffered and uses a macro defined BUFF_SIZE in the get_next_line.h
To change the buffer size being used simply edit the integer value for BUFF_SIZE and recompile the program.
This function along with a sample main can be downloaded and ran with a simple with the following commands inside a terminal.
$> git clone https://github.com/fractalfox01/get_next_line.git get_next_line $> cd get_next_line $> make $> ./get_next_line main.c ... ... output of main.c contents ... ...