Thread: looking for advice (kermi3 ?? salem?? )

I have a program that's right around 1,500 lines right now, and it's not even completed. The tedious part about it is, that it's just menu stuff. REALLY case and switch heavy. The only interesting part of it is using the if statements during the file executions to check if there were any errors. If there were errors, it displays a user friendly message while surpressing the program's technical message. I did it this way because I can predict the errors ( given the enviroment of the program ) that would occur, and setup if / else statements to handle them all. It's all in one function, as a menu style program executing the same exe 100 different times would get tricky trying to split into different functions. I'm fairly satisfied with how it's going. It executes fast, and does what it needs to do.

My question is, this has taught me some simple / beginner types of things. I have a running log file for the menu to also jot down errors and successful executions. Instead of searching for a tutorial that is probably 2nd grade, or not the best, from any of your expierences can you recommend any tutorials that are intermmediate? Or atleast detailed in walking you through some things, and getting the point accross on what exactly is happening in the given function?

I just think it's fun and challenging. You enjoy it, and hey, ya learn something!! I swear, i'm getting to the point of changing my signature to a quote from Johnny Five out of the movie Short Circuit. NEED MORE INPUT!! lol.

Thanks for any suggestions.

1500 lines in a single function

well dont ask us to debug it for you lol!!!

> can you recommend any tutorials that are intermmediate?
On what?
Testing?
Documenting?


Cooking and house cleaning....that's why I came here to ask such a question. The language in general. What you submitted I could do on my own and by the way some of the links are different colors, i've already been to them.

Heh i have about 3300 lines in my text adventure game and im not done with the combat or ... text part of it. I also have 0 bugs in my game, and can't see how some people can make so many and leave them in there. Anyhow, modulization can be helpful, like for me, my compiler's editor only allows 64k of information at a time to be loaded. However, I see no use for it, as of yet, to modulize everything. Nothing of mine can be reused that can't be made in 5 minutes. And sometimes making stuff reusable just so it can be could hinder your program. Now for the content portion of my post... Does anyone know why saving stuff takes so much memory nowadays? Take for example the dreamcast(no wars here) It takes just short of one full memory pack to save the information for a football season(not that I like sports anyhow). I feel that I could store all that information in a much smaller space than they do... is there something I'm missing?