Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
2 views1 page

Aa11 4

Uploaded by

1stsiteweb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views1 page

Aa11 4

Uploaded by

1stsiteweb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Chapter II

General rules

You can organize and name your files as you wish but your assignment has to comply
with the following rules.

• Your assignment must be written in C.

• Your assignment must comply with the Norm.

• Place all your files at the root of your repository.

• You have to compile your program using: cc

• You have to compile your program with the following flags: -Wall -Wextra -Werror

• You have to turn in a Makefile which will compile your source files. It must not
relink.

• Your Makefile must at least contain the rules: NAME, all, clean, fclean and re.

• Your functions should not quit unexpectedly (segmentation fault, bus error, double
free, and so forth) except for undefined behaviors. If it happens, your project will
be considered non-functional and your grade will be 0.

• You cannot use your libft.

• You are allowed to use the following functions:

◦ read
◦ write
◦ malloc
◦ free
◦ strerror
◦ The compiler directive: __asm__

• Your grade will be based on the speed, and thus the optimization of your program.

You might also like