ft_printf correction

Scale for project ft_printf

You should evaluate 1 student in this team

Introduction

Please comply with the following rules:

- Remain polite, courteous, respectful and constructive throughout the
evaluation process. The well-being of the community depends on it.

- Identify with the student or group whose work is evaluated the possible
dysfunctions in their project. Take the time to discuss and debate the
problems that may have been identified.

- You must consider that there might be some differences in how your peers
might have understood the project's instructions and the scope of its
functionalities. Always keep an open mind and grade them as honestly as
possible. The pedagogy is useful only and only if the peer-evaluation is
done seriously.

Guidelines

- Only grade the work that was turned in the Git repository of the evaluated
student or group.

- Double-check that the Git repository belongs to the student(s). Ensure that
the project is the one expected. Also, check that 'git clone' is used in an
empty folder.

- Check carefully that no malicious aliases was used to fool you and make you
evaluate something that is not the content of the official repository.

- To avoid any surprises and if applicable, review together any scripts used
to facilitate the grading (scripts for testing or automation).

- If you have not completed the assignment you are going to evaluate, you have
to read the entire subject prior to starting the evaluation process.

- Use the available flags to report an empty repository, a non-functioning
program, a Norm error, cheating, and so forth.
In these cases, the evaluation process ends and the final grade is 0,
or -42 in case of cheating. However, except for cheating, student are
strongly encouraged to review together the work that was turned in, in order
to identify any mistakes that shouldn't be repeated in the future.

- You must also verify the absence of memory leaks. Any memory allocated on
the heap must be properly freed before the end of execution.
You are allowed to use any of the different tools available on the computer,
such as leaks, valgrind, or e_fence. In case of memory leaks, tick the
appropriate flag.

Attachments

subject.pdf

Mandatory part

Gestion de conversion simple

Testez chacune des conversions sans aucun flag 'cspdiuxX%'

Testez les cas speciaux, comme 0, le plus petit int,
une chaine de caracteres vide ou un pointeur NULL.
Testez avec plusieurs arguments et conversions
Essayez les differents flags au millieu d'une phrase
(avec d'autres caracteres autour).

Yes No

Soyons fous

Refaites tous les tests mais, cette fois, verifiez que la
valeur de retour correspond a celle du printf original.
Essayez n'importe quelle combinaison de conversions.
Verifiez ce qui se passe avec des conversions identiques a la suite.
than MAXINT. The program must display "Error".

Yes No

Bonus

We will look at your bonuses if and only if your mandatory part is EXCELLENT. This means that you must complete the mandatory part, beginning to end, and your error management needs to be flawless, even in cases of twisted or bad usage. So if the mandatory part didn't score all the point during this defence bonuses will be totally IGNORED.

Gestion simple des flags

Verifiez les flags '.', '-' et 0.
Verifiez %-d avec INT_MIN
Verifiez le flag - avec n'importe quelle valeur.
Verifiez le "." avec plusieurs precisions.
Pour chaque test, la valeur de retour doit correspondre a celle du printf original.
Pour chaque flag fonctionnel, donnez 1 point
Si tous les flags fonctionnent, donnez 2 points

Rate it from 0 (failed) through 5 (excellent)

#, +, espace

Testez si les conversions marchent avec '#'+ et 'espace' avec n'importe quelle combinaison de flags
Chaque flag rapporte 1 point
Si tous les flags fonctionnent, rajoutez 2 points.