OOP
in [Programming]
|
Everything Responding to Gerardvignes... I've been looking at Aspect Oriented Programming (AOP - weaving or runtime) and Attribute Oriented Programming (@OP - directives or attributes use to mark up code). I wonder if either of these trends can justify being touted as the next generation of software developme... 17 Aug 2007 12:13
Mountains or Molehills I've been looking at Aspect Oriented Programming (AOP - weaving or runtime) and Attribute Oriented Programming (@OP - directives or attributes use to mark up code). I wonder if either of these trends can justify being touted as the next generation of software development? Structured Design was a great step for... 11 Aug 2007 16:49
Leader/Follower design pattern question Hi, While implemented for iterative handle (tcp socket) and and using iterative handle set (i.e. fdset in poll) must carefully deal with handles to avoid race conditions. Please, correct me If I'm wrong. Leader thread is blocked on poll() waiting for IO event (CONNECT, READ, CLOSE). New request arrives. Leader w... 21 Aug 2007 16:06
Storing intermediate objects (for "visual debugging") Hi everyone, currently I am working on some graphical software. Since it's not really possible to write classical unit-tests for this kind of problems the application is solving, I need to verify the results by seeing them. Which means that the intermediate data (let's call them resources) the software produces ... 10 Aug 2007 13:44
Pattern for user rights on form's objects Hi, I'm looking for an design pattern for objects that have to be visible or not under user rights. I'm mean for example: User A: Immortal user User B: Mortal user User C: stupid user Form has 3 buttons: New, Update and Delete User A can see and click on the 3 buttons User B can only click on New and Updat... 10 Aug 2007 04:41
How LoD is useful. On Mon, 06 Aug 2007 18:56:29 GMT, Daniel T. wrote: John Carter <joNhOn.ScPaArMteErV(a)EtRait.co.nz> wrote: ie. Ways in which bad designs allow us to subtly bypass the invariant protection. One of my favorite examples: struct Point { int x; int y; }; class Rectangle { ... 7 Aug 2007 04:12
How LoD is useful. (was: DbC, OOD and Stroustrup's Rule...) John Carter <joNhOn.ScPaArMteErV(a)EtRait.co.nz> wrote: ie. Ways in which bad designs allow us to subtly bypass the invariant protection. One of my favorite examples: struct Point { int x; int y; }; class Rectangle { public: Point& getTopLeft(); Point& getBotRight(); // invariant: /... 6 Aug 2007 19:28
DbC, OOD and Stroustrup's Rule, a concrete example The "spamfilter ate my homework" was not just an excuse, it really happened... Sigh! Anyhoo. With my earlier posts having met with confused silence and blank looks... ....let me plough on regardless. Let me reiterate a little... * If we propose that a class must have an invariant. - No... 8 Aug 2007 17:20
DbC, Stroustrup's rule and the OOD principles. On 01 Aug 2007 05:18:27 GMT, John Carter wrote: Here is an ambitious plan of attack.... Let's start with Bjarne Stroustrup's rule of thumb, convert it into an absolute rule and shake a few trees and see what falls out... [...] Now _every_ class does have an invariant...it's define by the valid re... 6 Aug 2007 15:19
Chapter II : DbC, class invariants, state space. In my previous post I contemplated converting Bjarne Stroustup's "Rule of thumb" into a Hard and Fast and Absolute rule. Namely now _every_ class does/must have an invariant. Furthermore, the invariant I suggested was "is this instance in the valid region of the class state space?" Now part of the whole poin... 1 Aug 2007 01:46 |