Anything. Well, common stuff like web frontends, log parsing, sysadmin task in general, but then some odd uses in which perl shines, too, amongst them:
- shell (well, job control is lacking still)
- patch e.g Windows DLLs (proprietary stuff) to convert English messages to German, and other random hackery on binaries
- make our Java Witnesses emit shrieks of horror and go dump core - things done while they still debate interfaces
- avoid touching the stinkin' crappy SAP GUI
- just prove "it's possible"
- bend and twist my OS to rendition
- decorate myself with an aura of rare weirdness for using such an exotic tool
- ... (to be continued)
So, little useful stuff, except where needed. (update) Needed things:
- tools for de-centralized management of centralized DNS and DHCP resources (think QIP)
- glueing handles to SAP
- directory (as in X.400, LDAP etc) munging
- ... (to be continued)
--shmem
_($_=" "x(1<<5)."?\n".q·/)Oo. G°\ /
/\_¯/(q /
---------------------------- \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
-
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.
|