Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I much prefer the option to create either an object orientated distribution, or a non-oo one.

If I don't need to keep any state, why bother with the added complexity? OO adds overhead, no matter how slight.

Among my list of familiar languages, Python is one. Python is "everything is an object". I'm a guy who prefers simplicity, and freedom to choose. If I want to create a list of functions for very basic mathematical calculations purely written in C fronted by Perl with no OO overhead, I like that choice. If I want to represent a Tesla vehicle that has thousands of always-changing parameters that requires a mechanism to maintain that state, I want that choice. When I want to wrap another language's API where I want to provide both a procedural and an OO interface, I want that choice. I feel that everything is an object is a bit overkill. That's why I didn't diverge with the then Perl6 crowd (in fairness, I did give it a very good run to be certain though).

Important part is the availability to choose. Even when I do write OO distributions (most of mine are), I don't use anything but the core perl OO functionality. No Moose or equivalents etc. Even when Corinna comes into play, I very much doubt I'll change my ways.

In reply to Re: What if Perl had an OO standard library? by stevieb
in thread What if Perl had an OO standard library? by awncorp

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (1)
As of 2023-06-06 02:38 GMT
Find Nodes?
    Voting Booth?
    How often do you go to conferences?

    Results (26 votes). Check out past polls.