This is a respose to both Juerd and crenz so I'll put the node here.
# # the short name by which your service will be known (cannot be 'my')
# Please document *why* something is not possible, instead of just "can't do this".
Because otherwise PerlSvc would not be able to read it.
# Do check the return values. In a module, it's better to turn PrintError off and handle errors yourself.
This ain't a module. The PerlSvc tool requires that the service name and the callbacks are in package PerlSvc. I think the info should contain a pointer to the PerlSvc docs and the "Perl Development Kit" should also be mentioned to prevent confusion.
Jenda
Always code as if the guy who ends up maintaining your code
will be a violent psychopath who knows where you live.
-- Rick Osborne
Edit by castaway: Closed small tag in signature
-
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.
|
