What do you mean partially interpretted?
The scripts are scripts. Unless Perl performs a compilation procedure to change parts of your script into machine code at run time, it is totally interpretted. There's nothing wrong with this.

Mind you, there are plenty of things you will never catch me doing in perl. It's a nice language, it's a useful language. I love it, BUT... You certainly CAN'T do some of the things that you can do in C or even in VB in perl. There is no inline assembly. Addressing memory is something you would have to do through a pm, with supplemental code. You'll never write an operating system or even load executable code (note I said load executable code, not run an executable), in perl, at least not perl 5.6, and not in any practical sort of way. Again, there's nothing wrong with this. Languages all have their niches. I would never do anything I use perl for in Prolog, but that doesn't mean that I'm going to abandon prolog. I think that people should be less "I'm a perl coder," "I'm a C/C++ coder," and more "I'm a coder, and I'm going to pick the appropriate language for this task." If nothing else, it is much more professional.

Just Another Perl Backpacker

---

---

• 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.