No. I wouldn't do a good enough job of explaining it, and don't have enough time to try, but the short story is: there are many means of expressing an algorithm that are equivalent in their expressiveness. That's the meat of Church's Thesis (one of the most important things to understand in computer science).

And that's not just pedantry, either. There are definitely fields of algorithms wherein the most natural way of expressing the algorithm is not procedurally. Take proofs by induction, for example: those are much more naturally represented functionally.

I think that maybe what's throwing you off is the definition of algorithm you've got there. That's simply not a good definition of the term, as it says "step by step". A better way of describing an algorithm would center more on the fact that it is a complete and unambiguous description of a way to solve a problem, not that it is "step by step". "Step by step" is sort of begging the question, if you will, of how that algorithm is represented (as "steps", in this case)... and that's really imaterial to what an algorithm is. 

------------
:Wq
Not an editor command: Wq

[download]

In reply to Re: coding of algorithms is inherently procedural by etcshadow
in thread coding of algorithms is inherently procedural by spurperl

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.