comment on

your 2nd and 3rd points are very questionable.

Very often Perl is more real-time than C.
Agree with me or not, but I saw several times a discussion when it appears that GCC is incapable to compile some large autogenerated programs, because it uses O(N*N) in many places. Therefore people bother splitting such sources to chunks.
Ideal programmer will create faster programs in C, but real-world programmers often write

for (i=0; i<strlen(s); i++) {
  // and never notice that counting lentgth is on every iteration
}
[download]

It is unrealistic to use advanced techniques on C everywhere,
in perl it is often hard to write bad: you often save precalculated values in hash, and so on.

As for 3rd item - embedding perl into different application is very common practice (well, cases when bytes count are exclusion, but those are rare, IMHO).

In reply to Re^2: What Perl CAN'T do? by Courage
in thread What Perl CAN'T do? by sanPerl

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.


XP is just a number
	PerlMonks