procedural-programming

When I am presented with programming problems, I naturally start breaking them up into logical objects in my head. Who has what responsibility, who owns what, who derives from what, etc. I am struggling with C. I just don't get how to do things in a Procedural Language. Can an experienced C programmer help explain how I should think about my programs during design time? For example, I want to write my own Semaphore class. I would naturally need a Queue data structure for my program, which I would like to write myself as well. If I needed to do this in Java or C#, I could simply whip up a quick

I've read the Wikipedia articles for both procedural programming and functional programming , but I'm still slightly confused. Could someone boil it down to the core? A functional language (ideally) allows you to write a mathematical function, i.e. a function that takes n arguments and returns a value. If the program is executed, this function is logically evaluated as needed. 1 A procedural language, on the other hand, performs a series of sequential steps. (There's a way of transforming sequential logic into functional logic called continuation passing style .) As a consequence, a purely