Sure, that handles it at the beginning. Not at the end.while(!is_roman(rdigit) && !IS_WHITE_SPACE(rdigit) && rdigit != EOF) return 0;
Just walk through it yourself with a debugger. Watch what happens when you enter an invalid roman numeral after some valid ones.
Also, if you come back to the problem with a fresh set of eyes after a bit of a drink and rest, sometimes it helps.
Do as I say, not as I do . . .
Experimentation is the essence of programming. Just remember to make a backup first.
"I'm a firm believer that <SomeGod> gave us two ears and one mouth for a reason - we are supposed to listen, twice as much as we talk." - LEAF
Questions posted by these guidelines are more likely to be answered.
Debian GNU/Linux user, with the awesome window manager, the git version control system, and the cmake buildsystem generator.
Hmm. I know.
I worked on this yesterday afternoon for like 5 hours.
now for 3 more. still can't get this thing to work.
I found something though,
it seems like if i enter XXXXA, it prints 40.
if i enter XXXXAA, it prints 40 then error msg.
if i enter XXXXAAAA, it prints 40, then error, flush the rest.
All my programs like to skip things on me.
Seems like you are right.
I moved the statement if it's not roman down with the statement EOF, it works now....
I'm gonna test more data, hopefully it works for everything!
Good to hear.
Let us know if something else goes wrong.
Remember: when in doubt, isolate the problem. If it's not comparing something properly, check both sides. If it's not printing errors, check the condition to print the errors. :P
Do as I say, not as I do . . .
Experimentation is the essence of programming. Just remember to make a backup first.
"I'm a firm believer that <SomeGod> gave us two ears and one mouth for a reason - we are supposed to listen, twice as much as we talk." - LEAF
Questions posted by these guidelines are more likely to be answered.
Debian GNU/Linux user, with the awesome window manager, the git version control system, and the cmake buildsystem generator.
I just have one question.
Why does it make a difference?
It's in the same function!!!
Because above, it's outside the loop, and only runs once.
When it's inside the loop, it runs every time the user enters something. Otherwise, outside the loop, it only gets executed whenever the function is, once per call of the function. Suboptimal, no?
Do as I say, not as I do . . .
Experimentation is the essence of programming. Just remember to make a backup first.
"I'm a firm believer that <SomeGod> gave us two ears and one mouth for a reason - we are supposed to listen, twice as much as we talk." - LEAF
Questions posted by these guidelines are more likely to be answered.
Debian GNU/Linux user, with the awesome window manager, the git version control system, and the cmake buildsystem generator.
gotcha!
Thanks so much
It's best if you actually make a flowchart for your code. Good for beginners.
Make it up exactly as you need the code to behave, then translate it to code.
Likewise, if it isn't working, then translate the code to a flowchart, make the necessary changes and translate it back.
Also, this type of code...
...is horrible to read, and thus not a good idea to do so. It's so easy to miss the last }.Code:if (x) { a; b; }
Instead, do something like...
Or if you REALLY, REALLY, REALLY want to save a line, you can doCode:if (x) { a; b; }
Code:if (x) { a; b; }
Originally Posted by Adak
As I pointed out in maybabier's other thread, there is a good guide to indentation here.
It really helps with debugging, trust me. The extra 20 seconds it takes to indent everything to the proper indentation level etc, often saves 20 minutes of frustration later on.
Anyhow, good luck with everything.
Do as I say, not as I do . . .
Experimentation is the essence of programming. Just remember to make a backup first.
"I'm a firm believer that <SomeGod> gave us two ears and one mouth for a reason - we are supposed to listen, twice as much as we talk." - LEAF
Questions posted by these guidelines are more likely to be answered.
Debian GNU/Linux user, with the awesome window manager, the git version control system, and the cmake buildsystem generator.
Except it will require logging in.
http://apps.sourceforge.net/mediawik...le=Indentation
Remove the "s" from the http and even guests can view it
ohh you guys are so helpful.
i usually am really neat about how i write the codes,
but when i get frustrated i just add on and erase where ever till i get it to work then fix it.
about debugging,
where do you usually put them?
