Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
LOL. I'm actually one of the original JSAN authors, so yes, I do count Javascript as a language. I actually prefer Java's OO to Perl's OO, for a number of reasons. (The main one is that classes are so 1990. Prototypes rawk my world.) And, it's not just the lack of namespaces, but the fact that you cannot safely mess with Object.prototype due to the lack of built-in associative arrays. Oh, and the fact that I have to know if a slot contains a function or not before I can safely access it. Ick!

As for SQL - it's not a programming language, it's a minilanguage designed to describe a resultset. In fact, I would argue it's not Turing-complete because you cannot step from one statement to the other like you can in Prolog. PL/SQL is even worse and it's palatable only because it's sometimes the only acceptable way to get Oracle to do what you need it to do.

I don't actually know many languages, but I know how to learn languages. I prefer knowing how to learn vs. actually knowing any day of the week. It's all about potential, baby! :-)


My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re^3: Professional imperative, objective, functional and logical perl by dragonchild
in thread Professional perl by mescanne

Title:
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?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others goofing around in the Monastery: (7)
As of 2024-03-29 11:39 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found