J
John Gabriele
The way I've always "designed" procedural C programs has just been to:
A. Think about what I need to do
B. Draw a flowchart with pencil and paper
C. Implement the flowchart in C from the top down
D. Compartmentalize chunks of code that serve some specific purpose
into functions, while filling in the framework left by the top-
down approach.
E. Refactor until I can call it pretty much done.
Though, I haven't created any large C projects myself (mostly just
programs consisting of maybe 5 to 10 source code files), so it could
be that the above process will land me in deep doo doo once my projects
start getting larger.
Any advice on procedural C program design?
Thanks.
--- if contacting via email, remove zees ---
A. Think about what I need to do
B. Draw a flowchart with pencil and paper
C. Implement the flowchart in C from the top down
D. Compartmentalize chunks of code that serve some specific purpose
into functions, while filling in the framework left by the top-
down approach.
E. Refactor until I can call it pretty much done.
Though, I haven't created any large C projects myself (mostly just
programs consisting of maybe 5 to 10 source code files), so it could
be that the above process will land me in deep doo doo once my projects
start getting larger.
Any advice on procedural C program design?
Thanks.
--- if contacting via email, remove zees ---