We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
I found this excercise confusing, ill-defined, unrealistic, and a waste of my time. However, following @Alexhans recommendation to solve this incrementaly is definitely the cure (short of having the answer handed to you).
If you are still trying to figure it out, here is my recommendation:
in whatever IDE (netbeans, eclipse, etc.) you are comfortable with, copy the locked code into your main file
now in your IDE, comment out all "undefined" student functions in the locked code so that your main compiles correctly, even if it does absolutely nothing useful yet
above the locked code that you copied into your IDE, write your #defines one at a time. As you go, uncomment the corresponding "undefined" student function, add a temporary cout << ... statement to troubleshoot your #defines or values in the main, and compile and test each #define as you go to make sure your #define's are successful and your cout statements produce what you expect.
I recommend you solve your defines in this order: INF, io(), toStr(), foreach(), and FUNCTION(). In my opinion, this list is ordered from easiest to hardest.
Short of giving you the answer or pointing you to an online resource (which you should definitely Google anyway), the biggest tip I can give: for a complex preprocessor directive like #define func(val1,val2,...,valn) <REPLACEMENT> you can put whatever you want into replacement and any call such as func(a,b,...,?) will be literally replaced with <REPLACEMENT> but on the inside of <REPLACEMENT>, val1 becomes a, val2 becomes b, ..., valn becomes ?. Also, in the <REPLACEMENT> area, #val1 becomes "a", val2##valn concatenates to b?.
I hope this helps. Literally the worst written crash-course in preprocessor directives, so if you are frustrated, give it rest, read up on #define, work on another problem, and come back to this one later once it clicks.
Good luck.
P.S. oh how frustrating it is that the markdown on this site is somewhat broken. I hope you are at least somewhat able to read my comment without getting a headache.
Preprocessor Solution
You are viewing a single comment's thread. Return to all comments →
I found this excercise confusing, ill-defined, unrealistic, and a waste of my time. However, following @Alexhans recommendation to solve this incrementaly is definitely the cure (short of having the answer handed to you).
If you are still trying to figure it out, here is my recommendation:
mainfilemaincompiles correctly, even if it does absolutely nothing useful yet#defines one at a time. As you go, uncomment the corresponding "undefined" student function, add a temporarycout << ...statement to troubleshoot your#defines or values in themain, and compile and test each#defineas you go to make sure your#define's are successful and yourcoutstatements produce what you expect.INF,io(),toStr(),foreach(), andFUNCTION(). In my opinion, this list is ordered from easiest to hardest.Short of giving you the answer or pointing you to an online resource (which you should definitely Google anyway), the biggest tip I can give: for a complex preprocessor directive like
#define func(val1,val2,...,valn) <REPLACEMENT>you can put whatever you want into replacement and any call such asfunc(a,b,...,?)will be literally replaced with<REPLACEMENT>but on the inside of<REPLACEMENT>,val1becomesa,val2becomesb, ...,valnbecomes?. Also, in the<REPLACEMENT>area,#val1becomes"a",val2##valnconcatenates tob?.I hope this helps. Literally the worst written crash-course in preprocessor directives, so if you are frustrated, give it rest, read up on
#define, work on another problem, and come back to this one later once it clicks.Good luck.
P.S. oh how frustrating it is that the markdown on this site is somewhat broken. I hope you are at least somewhat able to read my comment without getting a headache.