Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

Re: What are the core points of good procedural software design? (functions, code structuring)

by kabeldag (Hermit)
on Jun 23, 2008 at 04:29 UTC ( [id://693437]=note: print w/replies, xml ) Need Help??


in reply to What are the core points of good procedural software design? (functions, code structuring)

Thinking about what steps need to be taken before starting out is always good (planning/thinking/brainstorming). Identifying input and output of each step, then modularizing that step into a sub should eliminate a few globals. If the entire process of getting from A to B is a bit of a long one (A to Z), then move your modularized subs into a separate library (Perl Module). Once you have modularized everything, then the kick off / entry point of the journey should be become apparent, though it should have been apparent at the start.

Somebody else will no doubt provide a good list of points in regard to the overall approach. All I can say is to modularize, modularize and modularize...(:-\)

  • Comment on Re: What are the core points of good procedural software design? (functions, code structuring)

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://693437]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (5)
As of 2024-04-25 15:14 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found