I haven't mentioned functional programming simply because I've never wrote anything in functional languages (with exception for very small Emacs Lisp snipplets in my .emacs). In fact I have no opinion about them and I'm not ready to discuss them. My post was about 'OO vs. procedural'. Take this note in consideration before reading my reply.

I haven't said that several styles cannot work together. Moreover nothing in procedural programming actually implies bad design decisions. However I believe that for big projects human brains just cannot handle functional design. We have to create abstractions and it is easier for us to handle relationship between several classes of objects than relationship between numerous states of data structures and network of procedures (aka "call tree").

This is why I think humans can write better code (in big projects) when they follow mainly OO design (vs. procedural).

However in the bounds of some abstraction procedural design is acceptable probably (like in your example where actual event processor is quite isolated thing).

--
Ilya Martynov (http://martynov.org/)

In reply to Re: Re: OO design vs. procedural design by IlyaM
in thread From the Void and into the Light... by Dogma

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.