Re: I/O class: how to design for special case
- From: jladd@xxxxxxxxxxxxxx
- Date: 27 Jan 2006 15:10:44 -0800
Simon,
I think you have go it sorted out now. The key that you have uncovered
is getting
CFooBuffer to have the methods, abstract, virtual or otherwise. :)
>>But the design is starting to become more complex and harder to use.
OO systems take a little more time to create, but you will make this
time back the first time
you need to modify the system for a new buffer type or fix a bug.
Good luck with your implementation(s).
Rgs, James.
.
- Follow-Ups:
- Re: I/O class: how to design for special case
- From: Simon Elliott
- Re: I/O class: how to design for special case
- References:
- I/O class: how to design for special case
- From: Simon Elliott
- Re: I/O class: how to design for special case
- From: H. S. Lahman
- Re: I/O class: how to design for special case
- From: Simon Elliott
- Re: I/O class: how to design for special case
- From: H. S. Lahman
- Re: I/O class: how to design for special case
- From: jladd
- Re: I/O class: how to design for special case
- From: Simon Elliott
- Re: I/O class: how to design for special case
- From: jladd
- Re: I/O class: how to design for special case
- From: Simon Elliott
- I/O class: how to design for special case
- Prev by Date: Re: OOP phrases
- Next by Date: Re: Simple inheritence question
- Previous by thread: Re: I/O class: how to design for special case
- Next by thread: Re: I/O class: how to design for special case
- Index(es):