Well, you wrote:
The client only does stuff through the accessors, so you don't have the coercion issues.
which sounds specific enough to me, and that was what I argued against.

You are right about that it's good to do the design first (if only all programmers would). It's also good to have an API, but that's already implied if you are using an ADT, because it wouldn't be much of an ADT if you'd poke around in the datastructure outside of defined set of functions. However, you do not need objects to be able to deal with ADTs. Your password file can be seen as an ADT which you access via the *pwent set of functions.

Abigail

In reply to Re: Help with ADT by Abigail-II
in thread Help with ADT by dimmesdale

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.