On the conceptual level, yes. A good number of API's don't actually start as API's. Once they work into that larger scheme of maintainability, they need to be carefully thought out according to the current methods and procedures that they need to fit right now. In doing that initial evaluation, you also need to look at how they are going to evolve as best you can.

Right now I deal with this since we have our own authentication services for our labs and I have to maintain a legacy "API," if you will. Half of the code is well structured. The other half is spaghetti. Let's just say that there are a lot of programmers here who enjoy global variables. A lot of global variables...

Firm evaluation of the API needs to accomplish the task at hand, as well as be open for expansion. I enjoy C++'s expansionability as well as Java and Perl's. It just depends on the task at hand. I'm pulling a lot more things into Perl because of code handling (plus management has finally smiled on Perl for development and is questioning our evil proprietary WinBatch crap), and because of general love of the language.

In reply to Re: API Interfaces by iamnothing
in thread API Interfaces by zakzebrowski

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.