Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

Comment on

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

I spent quite some time programming in Scheme and Haskell a year or two ago. Both are very nice programming languages, but I always slide back to Perl. It's difficult to ascertain why, but some reasons include:

  1. Perl is everywhere. Scheme or Lisp compilers and interpreters are not, and they are sometimes harder to install. Same goes with Haskell. This isn't a chicken and egg problem for Lisp anymore; it's been around for 50 years.
  2. Perl integrates. CPAN. No such thing for Lisp or Haskell yet, which makes it awkward to be lazy. (Or: you spend more time re-inventing the wheel and steam engine.)
  3. Perl is good enough. The only things I'm missing from Scheme and Haskell are macros, less convoluted syntax, and static types -- all of which can be found in Perl 6.

However, I heartily recommend both programming languages. It gives you more perspective and problem-solving strategies even if you never switch permanently over.

--
print "Just Another Perl Adept\n";


In reply to Re: (OT) Has anyone gone from perl to lisp? by w-ber
in thread (OT) Has anyone gone from perl to lisp? by leocharre

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, 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, 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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    [Corion]: LanX: Then the problem should persist without encoding to base64 too ;)
    [LanX]: I think it's a flag problem ... I'll produce a reprodocable example for SOPW
    [Corion]: "flag problem" to me sounds like "contains UTF-8 bytes but was never properly decoded to an UTF-8 string"
    [LanX]: not my code ...
    [choroba]: yeah, sounds like one of the strings is not flagged as UTF-8
    [choroba]: which usually means its input wasn't handled correctly
    [Corion]: choroba: Yeah, I think that would be the good solution
    [LanX]: I suspect the first string which comes from the DB ...
    [LanX]: ... but this part is already in production for a year now
    [Corion]: LanX: The "good" approach here would be to use the appropriate DBI parameters to make the driver decode strings properly. But that will have a ripple-on effect of messing up all the places where manual decoding happens ;)

    How do I use this? | Other CB clients
    Other Users?
    Others examining the Monastery: (11)
    As of 2017-01-16 13:55 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      Do you watch meteor showers?




      Results (150 votes). Check out past polls.