IMHO, object-oriented approaches are a very, very small increment away from typical imperative/procedural programming - largely just a different wrapping on scope. Traditional OO is solidly in the imperative camp.
Kemp Watson -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Scott Parish Sent: March 29, 2007 4:27 PM To: Mozart users Subject: Re: Overview of principal programming paradigms The description of imperative programming on wikipedia is: In computer science, imperative programming, as contrasted with declarative programming, is a programming paradigm that describes computation as statements that change a program state. In much the same way as the imperative mood in natural languages expresses commands to take action, imperative programs are a sequence of commands for the computer to perform. A commonly used synonym to imperative programming is procedural programming. From the tiny bits of dabbling i've done with smalltalk, it very much doesn't seem very declarative. Further, its very much about state. Sure, you affect the state via a pattern called message passing, but its still about "statements that change a program state (one object at a time)" I had never before thought about OOP as being imperative, but i think i'm convinced. sRp -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.20/737 - Release Date: 28-Mar-2007 4:23 PM
_________________________________________________________________________________ mozart-users mailing list [email protected] http://www.mozart-oz.org/mailman/listinfo/mozart-users
