Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

comment on

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

I have to say, I am probably one of your 'target audience'. I'd like to think I'm open to change so I'd like to hear more specifics about why or perhaps where perl fits in as a scientific application.

As a physics undergrad, I was taught Fortran (well, a bit) and supervisors, friends and profs used Fortran or C for numerical simulations. At $work, I learned perl, mostly because I was getting p****d off at shell scripting! But I'm glad I did because I came to like perl in its own right. However, when writing numerical simulations at work, I (have to) use C or C++.

My boyfriend (working for a PhD in image forensics) swears by python for its numpy and scipy libraries, but again writes most of his processing intensive code in C.

So the perception is definitely there in my mind. I'm your perfect stereotype---Perl is great for its ease of use, flexibility and text processing capabilities, but C/C++ and python are the way to go for science, at least that's the impression I've always been given by the people around me. So what is it specifically that makes perl suitable/better for these applications? Or what needs doing to make perl better? Writing libraries? Or do you think it's only a matter of perception?

Those are my principles. If you don't like them I have others.
-- Groucho Marx

In reply to Re: Perl for science by why_bird
in thread Perl for science by punkish

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 making s'mores by the fire in the courtyard of the Monastery: (3)
As of 2023-06-10 17:27 GMT
Find Nodes?
    Voting Booth?
    How often do you go to conferences?

    Results (39 votes). Check out past polls.