2009-01-17, 12:35 AM
(This post was last modified: 2009-01-17, 12:53 AM by KajitiSouls.)
I do not have time to look over the code thoroughly atm, but I'll try to comment as soon as I'm able =)
I'm fairly sure others will agree with me on this, but I would request that you present your java code in [NOPARSE][/NOPARSE] tags. Additionally, make the code inside the methods and for-loops and whatnot indented; a single space is just fine. This is so the code is more readable!
Right off the bat though, I'd say that the goBack method doesn't work as one would assume it would. I mean, why does Karel need to turn left after going back? The main reason I complain is because it can be a bit confusing to others, and who knows, maybe you'll confuse yourself too. The latter will definitely happen if you decide to look at the code a month later or something.
EDIT: For making programs, it takes time. Think about what objects you need, how you'll go about telling the computer what to do, etc. If anything, practice makes you a lot faster with programming. Knowing what kind of standard tools you have also helps. For example being able to use Hashtables for instant data recall as opposed to parsing through a huge array to see if something exists.
Java API
Just look for what you need, don't worry about what the rest of this stuff means, especially if you're not going to use it.
Btw, I don't think you really need to use the API for this particular problem. I just put it up so you can use it as a reference.
I'm fairly sure others will agree with me on this, but I would request that you present your java code in [NOPARSE][/NOPARSE] tags. Additionally, make the code inside the methods and for-loops and whatnot indented; a single space is just fine. This is so the code is more readable!
Example Code
Right off the bat though, I'd say that the goBack method doesn't work as one would assume it would. I mean, why does Karel need to turn left after going back? The main reason I complain is because it can be a bit confusing to others, and who knows, maybe you'll confuse yourself too. The latter will definitely happen if you decide to look at the code a month later or something.
EDIT: For making programs, it takes time. Think about what objects you need, how you'll go about telling the computer what to do, etc. If anything, practice makes you a lot faster with programming. Knowing what kind of standard tools you have also helps. For example being able to use Hashtables for instant data recall as opposed to parsing through a huge array to see if something exists.
Java API
Just look for what you need, don't worry about what the rest of this stuff means, especially if you're not going to use it.
Btw, I don't think you really need to use the API for this particular problem. I just put it up so you can use it as a reference.

