VBC Test

[manuelgalvez192]

Hello, I'm a student who has been using the tool to practice for the exam. First of all, thank you for creating such a practical and useful tool. I wanted to ask about the VBC tests. There are certain tests, such as sending "abc" as a parameter that expects a numeric result. In my opinion, an alphabetic character is an unexpected character; it shouldn't display 0. As I said, there are several such tests, such as unclosed parentheses, which in the test state that they expect the result of the operation, but according to the subject's own examples, they shouldn't.
$> ./vbc '1+2)' | cat -e
Unexpected token ')'$
If I'm wrong, it would be great if you let me know so I can prepare better. Thank you very much in advance.

[terminal-42s]

Hi manuelgalvez192,

Thank you for bringing up these important points about the VBC tests. I understand the confusion regarding how certain unexpected inputs (like alphabetic characters or unclosed parentheses) are handled.

• The subject’s examples clearly state that inputs like 'abc' or '1+2)' should result in an error message (e.g., “Unexpected token”).
• However, some tests expected numeric results for these cases, which contradicts the subject’s own rules.

What I Did:
I reviewed the tester and updated it to align with the subject’s examples. Now, inputs like 'abc' or '1+2)' will correctly output an error message instead of a numeric result.

Example:

$> ./vbc 'abc' | cat -e
Unexpected token 'a'$
$> ./vbc '1+2)' | cat -e
Unexpected token ')'$

This change ensures consistency with the subject’s requirements and helps students prepare more accurately for the exam.
If you notice any other discrepancies or have suggestions, please let me know!