Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

The fourth paradigm is... 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • FWIW, back at Uni we actually have the following classes: Programming Paradigms I, II, III and IV.

    What we learn in these classes is, respectively, Functional, Imperative, Logic and OO programming.

    In my case, this was done mostly with Haskell, C, Prolog and Java (sometimes they change the languages).

    There was also a teacher who used to say that databases are a paradigm on its own.

    Also, I was first introduced to Perl in the classes of "Scripting as a Programming Paradigm".
    • > What we learn in these classes is, respectively,
      > Functional, Imperative, Logic and OO programming.

      Yep, those are the four that I identified in my last post. However, I argue that OO is an "abstraction style", and not a "control style", which is what I'm looking for.

      • If you want a control style, where does event-driven programming fit? What if it's asynchronous?

        • > If you want a control style, where does
          > event-driven programming fit? What if it's
          > asynchronous?

          I define the control paradigm by the input (code) and the output (what happens when you run it). In the event driven case, you give it actions to execute when certain things happen. But the first part is the important part, you're giving it actions, and it tells you what happens when those actions are executed, even though those actions are triggered rather than sequenced. Therefore, I think event
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.