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.

- Remember that for the duration of the defence, no segfault, no other unexpected, premature, uncontrolled or unexpected termination of the program, else the final grade is 0. Use the appropriate flag.
You should never have to edit any file except the configuration file if it exists. If you want to edit a file, take the time to explicit the reasons with the evaluated student and make sure both of you are okay with this.

- 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

Simple Conversion Management

  • Simply check each conversion without any flags 'cspdiuxX%'
  • Try special cases like 0, or smallest int, or empty string, or NULL pointer.
  • Test multiple arguments/conversions.
  • Test various conversions in the middle of a sentence (put other characters before and/or after).

Get Crazy

  • Redo every previous test but this time verify that the return value matches the one of the original printf.
  • Try any combination of conversions.
  • Check what happens with a series of identical conversions following each other.

Bonus part

Evaluate the bonus part if, and only if, the mandatory part has been entirely and perfectly done, and the error management handles unexpected or bad usage. In case all the mandatory points were not passed during the defense, bonus points must be totally ignored.

Simple flags management

  • Check the flags '.', '-' and 0.
  • Check the %-d with INT_MIN
  • Check the - flag with any value.
  • Check the 0 flag like %04d.
  • Check the '.' with multiple precisions.
  • For every test, verify the return value matches the original one.
  • For each working flag, give 1 point.
  • If all the flags work, give 2 bonus points.
Rate it from 0 (failed) through 5 (excellent)

# + space

  • Check all the conversions with the flags '#', '+' and space with all the other flag combinations.
  • For each working flag, give 1 point.
  • If all the flags work, give 2 bonus points.
Rate it from 0 (failed) through 5 (excellent)

Ratings

Don’t forget to check the flag corresponding to the defense