Hey guys, I was looking into c++ console programming design and I know that pseudocode can be used but are there any other techniques can be used for a non object oriented program?
Thanks.
Hey guys, I was looking into c++ console programming design and I know that pseudocode can be used but are there any other techniques can be used for a non object oriented program?
Thanks.
You're talking like pseudocode was some sort of design method. Procedural programming is procedural programming. It's very straight forward. You do this, then you do this, then you do this until this happens, then you do this... etc, etc...
There is no real technique to it. Just be as standard as possible.
Sent from my iPadŽ
I see thanks for your help and once again sorry for a newbie question.
Ask another newbie question and I'll report you!
Seriously, stop apologizing. I've seen questions 100 times worse, and besides we all have to start somewhere sometime.
Sent from my iPadŽ
Are you looking for something like flow charts? They are a nice alternative to Pseudocode.
Last edited by Kurisu; 02-15-2006 at 09:03 PM.
I will do some research on flow charts do you know of any good examples?
here's an image of a basic flowchart:
http://www.rff.com/basic_flowchart_house_painting.htm
It uses the process of painting a house as an example.
The squares represent functions or actions to perform while diamonds are choices often coded as ifstatements.
A flowchart basically allows you to visually represent the flow of your program before you code it. Saves you alot of time and errors later as you can map out all possibilities with a flowchart then simply convert it to code.
Here is a more lengthy version.. say if you were coding a car simulator for manual transmission:
http://www.rff.com/stick_shift_flowchart.htm
Last edited by Kurisu; 02-15-2006 at 11:09 PM.
Well there are also:
Structure Charts
and
Nassi Schneiderman Diagrams
Mr. C: Author and Instructor
I'd so tearup that carOriginally Posted by Kurisu
pseudocode is way overrated. If you can code it in pseudocode why not code it in real code instead and just fill in the blanks afterwards (like type declarations and error handling?).
charts are far better, whether flowcharts or the more modern sequence diagrams.
I should probably get around to using a design method but I never bother. Just finished a puny 8KB (or 210 line) program without bothering to design it first. Virtually everything is in main but oh well.
Back to the subject a bit, I'd probably use a flowchart for showing how the general sections of the program work and then use pseudocode for those sections.
Generally, I use flowcharts while designing the large picture. Then I find the parts that should be fleshed out a bit before coding, where there is easily a loss of efficiency and/or it is just a part that would be hard to code on the fly, and psuedocode them.
