/printf

This is our first ALX project

Primary LanguageC

233CA0A6-976A-43DE-BCCC-670442922ECC

WRITING OUR OWN PRINTF FUNCTION

AUTHOR

Joshua Akinbode and Gift John 0659D7F2-DFEF-47A9-8E74-CCB1750925CA

Resources

Read or watch:

. Secrets of printf

. Group Projects Concepts page

. Flowcharts Concept page

Requirements

General

. Allowed editors: vi, vim, emacs
. All your files will be compiled on Ubuntu 20.04 LTS using gcc, using the options -Wall -Werror -Wextra -pedantic -std=gnu89
. All your files should end with a new line
. A README.md file, at the root of the folder of the project is mandatory
. Your code should use the Betty style. It will be checked using betty-style.pl and betty-doc.pl
. You are not allowed to use global variables
. No more than 5 functions per file
. In the following examples, the main.c files are shown as examples. You can use them to test your functions, but you don’t have to push them to your repo (if you do we won’t take them into account). We will use our own main.c files at compilation. Our main.c files might be different from the one shown in the examples
. The prototypes of all your functions should be included in your header file called main.h
. Don’t forget to push your header file
. All your header files should be include guarded
. Note that we will not provide the _putchar function for this project

Authorized functions and macros

. write (man 2 write)
. malloc (man 3 malloc)
. free (man 3 free)
. va_start (man 3 va_start)
. va_end (man 3 va_end)
. va_copy (man 3 va_copy)
. va_arg (man 3 va_arg)

Compilation

 Your code will be compiled this way:
. $ gcc -Wall -Werror -Wextra -pedantic -std=gnu89 *.c
. As a consequence, be careful not to push any c file containing a main function in the root directory of your project (you could have a test folder containing all your tests files including main functions)