By Mr. Horsley's logic, English (or any other natural language) is a "write-only language" because there are so many ways of saying things.

He's right.

If you don't believe me, construct a parser to correctly decipher the meaning of an English sentence, or to reject it if the sentence is not valid.

It's hard. Very, very hard. English is a mess. It's one of the hardest languages to learn for a reason: it's huge, and it's inconsistent, even compared to other natural languages.

We have a whole host of ways to write negation: "not hopeful", "atypical", "unrelated", "disproportional", "counterintutive", "antiestablishment". That's not an exhaustive list. "Up" opposes "down", but "to burn up" is not the opposite of "to burn down".

The language is ambiguous, even at it's most basic levels: In the sentence: "He finished his bow, and walked off briskly", the actor could be a bowyer or an actor, but we can't know without more contextual information. Languages that resolve ambiguity due to context are harder to understand: English does it a *lot*. And despite training, we can't really manage to learn it all.

Everyone in every English-speaking nation that I can think of is legally required to attend a *minimum* 11 years of schooling, where they learn spoken and written English, and formal rules of grammar and composition. Despite this, few native speakers understand even the most common English language idioms.

For example, I don't know how many times I've read people who should know better write: "to tow the line" (to tug on a rope!) rather than "to toe the line" (to step carefully along a pre-set path) as an idiom for obedience to authority. They should know better after 11 years: but they don't.

That's only true if you only learn one way of saying things, or a small sub-set of the vocabulary. Then you can't understand what someone else is saying, if s/he chooses to use a different phrase.

Name ten people who know every single word in the Oxford English Dictionary, every meaning in every context. I don't know any; and I know a lot of teacher and English majors. I doubt you know anyone who does, either. Everyone speaks a subset of English; and that's a problem. Try talking to someone straight from Jamaica: you won't understand him. You won't understand someone straight from old-world Scotland: as one of my friends was quite rudely told, "Yae dinnae ken hae tae tawk raeght!"

English is a mess. Worse, yet, literary English is confounded by a whole host of metaphor, much of which only makes sense only if you have a grounding in classical mythology. If you disagree, well, perchance we might stridently take discourse in the temple of Mars, good sir! Engarde! :-P


In reply to Re^2: Perl for big projects by Anonymous Monk
in thread Perl for big projects by CountZero

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.