From my pov I would not write the following things in perl:
- Complex multi-threaded programs (because objects/structures can not be shared and function pointers can not be used cross-threads) as well. Library support for simple multi-threaded things like async IO is not good. It is also not acceptable that it is unclear if a CPAN module supports multi-threading or not.
- Complex GUIs - Tk has a old-fashioned look-and-feel. Other GUI kits need to improve on stability and documentation. The thread issue is even bigger with complex GUIs as you need to pass around objects between the two things.
- Shared objects - nearly impossible to roll out perl as a COM object or a shared library for other platforms. It is also very painful to acess shared objects.
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>
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
Want more info? How to link
or How to display code and escape characters
are good places to start.