RE: adding key to DB object
From: Brandon Metcalf (bmetcalf_at_nortel.com)
Date: 03/29/05
- Next message: Brandon Metcalf: "embedding DB handle in object (was RE: adding key to DB object)"
- Previous message: David Nicol: "Re: cacheing problem"
- In reply to: Will Rutherdale: "RE: adding key to DB object"
- Next in thread: Brandon Metcalf: "embedding DB handle in object (was RE: adding key to DB object)"
- Reply: Brandon Metcalf: "embedding DB handle in object (was RE: adding key to DB object)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 29 Mar 2005 15:32:39 -0600 (CST) To: "Rutherdale, Will" <Will.Rutherdale@sciatl.com>
W == Will.Rutherdale@sciatl.com writes:
W> For the same reason you wouldn't modify data in a C structure belonging
W> to
W> an API you're using. It violates the general software engineering
W> principles of information hiding and encapsulation. There are all kinds
W> of
W> reasons putting your own data into an API's structure is bad, for
W> instance
W> if the implementation changes then your trick may no longer work, and
W> your
W> code will not be portable to new versions of the library.
Understood.
-- Brandon
- Next message: Brandon Metcalf: "embedding DB handle in object (was RE: adding key to DB object)"
- Previous message: David Nicol: "Re: cacheing problem"
- In reply to: Will Rutherdale: "RE: adding key to DB object"
- Next in thread: Brandon Metcalf: "embedding DB handle in object (was RE: adding key to DB object)"
- Reply: Brandon Metcalf: "embedding DB handle in object (was RE: adding key to DB object)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|