What I was driving at was that he wasn't quite sure how the ADT was going to be specified. In fact, he says that the ADT's definition is constantly changing. This implies, to me, that he's using this thing. By creating some API, he is able to deal with the ADT in some abstract manner within the client. He gets to figure out what exactly he wants this thing's behavior to be.
Then, and only then, does he have enough information to be able to actually design the darn thing. He's trying to put the cart before the horse.
For example, I only skimmed the original post, but I'm pretty sure that he doesn't need one ADT, but a composition of ADT's.
------
We are the carpenters and bricklayers of the Information Age.
Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.
In reply to Re: Re: Help with ADT
by dragonchild
in thread Help with ADT
by dimmesdale
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |