C Piscine Exam 01 [2021] ★ Working & Plus
🏊 C Piscine Exam 01: Survival Guide Exam 01 is usually the second test in the 42 Piscine (Week 2) and is a significant step up from Exam 00. While Exam 00 focused on basic logic and character manipulation, Exam 01 starts testing your understanding of standard C concepts and command-line arguments. 🛠️ Core Topics to Master
The difficulty of exercises is progressive. If you haven't mastered these by Friday, you'll likely hit a wall:
Pointers: You must be comfortable with pointer basics, including "pointer to pointer" concepts often seen in the C01 module (e.g., ft_ultimate_ft).
Command Line Arguments: Expect problems involving argc and argv. A common strategy is to finish the C06 project before this exam, as it directly covers these concepts.
String Manipulation: Standard tasks like ft_strlen, ft_putstr, or basic string searching/reversing are staples.
Memory Management: Basic familiarity with malloc and free is often required at this stage. 💻 Typical Exam Setup & Rules c piscine exam 01
Accessing the Exam: You log in with the username/password exam / exam.
The Examshell: Once logged in, type examshell in the terminal and log in with your personal credentials to begin.
Submission: Use the grademe command to submit. Remember to git add, commit, and push your code to the rendu/ directory before typing grademe.
The "0 Score" Trap: If you fail an exercise, you get 0 for that level. You usually need at least 25 points to "validate" the exam. 💡 Pro-Tips for Success
Skip Shell01 (If Needed): Don't spend too much time on Shell exercises mid-week. Focus on C00, C01, and C06 to prepare for the coding logic needed in the exam. 🏊 C Piscine Exam 01: Survival Guide Exam
Vim is Your Friend: Don't rely on VSCode. It may not be available or stable on the exam machines. Knowing basic Vim navigation is a life-saver.
Don't Leave Early: Even if you get stuck, stay until the end. Sometimes a second look at a problem after an hour makes it click.
Use Your Traces: After a failed grademe, look at the trace files to see exactly why your code failed (e.g., wrong output, hidden test cases).
Ready to start your prep? Check if you can comfortably code ft_putstr or a program that prints its arguments in reverse—these are great benchmarks for Exam 01 readiness. felixtanhm/42-piscine - GitHub
Level 4 (Rare but possible)
ft_itoa– Convert an integer to a string. You must handleINT_MIN(which is-2147483648– multiplying by-1causes overflow, so handle it separately).ft_list_push_front/ft_list_size– If your Piscine introduces linked lists early, expect basic list manipulation. You must understandt_list *head.
Final Thoughts
Exam 01 separates those who truly internalized pointers and memory from those who memorized syntax. The most deceptive exercise is often ft_putnbr – writing it recursively while handling -2147483648 is a rite of passage. Pass this, and you’re ready for Exams 02–04, where linked lists and printf-like functions await. ft_itoa – Convert an integer to a string
“The exam doesn’t check if you know the answer – it checks if you can find it without Google or a compiler.”
Here’s a complete feature breakdown for "C Piscine Exam 01" — typically the first graded exam in the 42 Network’s C Piscine.
Exercise: ft_atoi_base
Convert a string (in a given numeric base, e.g., binary, hex) into an integer. This requires handling +/- signs, whitespace, and invalid characters. It is the ultimate test of string traversal.
Why it's hard: You have to track sign, manage overflow (informally), and validate the base string (no duplicates, no +/-).
11. I/O
- stdio.h: printf, scanf, fgets, puts, getchar, putchar
- Use fgets for safe line input:
char buf[100]; if (fgets(buf, sizeof buf, stdin)) ... - fopen, fread, fwrite, fclose for file I/O
- Check return values for errors (EOF, NULL)
14. Style & Best Practices
- Initialize variables.
- Prefer meaningful names.
- Keep functions small and single-purpose.
- Comment complex logic.
- Check return values of system/library calls.
- Avoid undefined behavior.
