Re: how to store list of varying types
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Tue, 01 Jul 2008 10:50:16 -0400
Good point. I always tell people "design the data structure FIRST" Once that is done,
the coding is easy.
joe
On Mon, 30 Jun 2008 23:26:31 -0700, DB <abc@xxxxxxxx> wrote:
Nick Schultz wrote:Joseph M. Newcomer [MVP]
I am writing a program that parses data found in a proprietary protocol
packet into individual chunks of varying sizes, based on the Opcode tag of
the packet. sizes could be from a single byte to an very large null
terminating string. The parser is part of a pipeline that works on the
incoming packets so that an user at the end can do whatever he/she wants to
do with the data (display it, apply operations, etc)
Why not do so then?
To wit, you create objects according to your paradigm. Delegates to
proxy options are available. And, they are usually one in the same.
There is still a tenancy to think from the top down, procedural if you
will. Think about the fundamental object you need and build from that
for the simplest start. It may not encompass what you need, but, if you
follow the rules of encapsulation, you will have little trouble of
extending your thoughts.
Best, Dan.
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- References:
- Prev by Date: Re: how to store list of varying types
- Next by Date: Re: Book recommendations
- Previous by thread: Re: how to store list of varying types
- Next by thread: Re: "writefile" fails with error number 5 = Access is denied
- Index(es):
Relevant Pages
|
