<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Karl,<br>
<br>
my approach has been that we should make the plugin writers life
easier, even if learning a bit more about how to write a plug-in
becomes a necessity. So I am looking to replicate the framework
approach from Perl into C. Big advantage that C will have is that it
will be able to lots of things at compile time, that Perl gets to do a
invocation time. Big disadvantage is the library will be a much larger
body of work and I am putting it off until I can assume I have the Perl
framework sufficiently stable to act as an exemplar of what to achieve
if not a how to achieve it. I have thought about using a embedded Perl
interpreter in the 'C' code plugins. But I assume this would go down
like a lead balloon for performance reasons!<br>
<br>
Regards, Howard.<br>
<br>
Karl DeBisschop wrote:<br>
<blockquote type="cite"
cite="mid20040331015144.0a293d0e.karl@debisschop.net">
<pre wrap="">On Tue, 30 Mar 2004 20:23:24 +0100
Howard Wilkinson <a class="moz-txt-link-rfc2396E" href="mailto:howard@cohtech.com"><howard@cohtech.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">A simple patch for check_by_ssh which produces usage output on a
single line. This is a quick fix to providing a Usage parsing
interface.
</pre>
</blockquote>
<pre wrap=""><!---->
Now I see why you disregarded the existing developer guidelines so many
times.
Could the usage parsing interface be done at the source level?
The reason I ask is because we really need a tool to do it there anyway.
Several times we have either provided an option and failed to document
it, or provided documentation for an option that was not added to the
getopt array or was not handled on the getopt processing.
So I have come to believe we need a cdoe checker for that case. It would
seem that a usage parse tree would be a natural outcome of such a
checkier. And would tie into discussions about embedded docbook
documentation which could be used to generate help doc in man page,
html, or PDF format.
--
Karl
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<title>Signature</title>
<table cellpadding="2" cellspacing="2" border="0"
style="text-align: left; width: 100%;">
<tbody>
<tr>
<td style="vertical-align: top;">Howard Wilkinson<br>
</td>
<td style="vertical-align: top;">Phone:<br>
</td>
<td style="vertical-align: top;">+44(20)7690 7075<br>
</td>
</tr>
<tr>
<td style="vertical-align: top;">Coherent Technology Limited<br>
</td>
<td style="vertical-align: top;">Fax:<br>
</td>
<td style="vertical-align: top;">+44(20)79230110<br>
</td>
</tr>
<tr>
<td style="vertical-align: top;">33 Belgrade Road, Stoke
Newington,<br>
</td>
<td style="vertical-align: top;">Mobile:<br>
</td>
<td style="vertical-align: top;">+44(7980)639379<br>
</td>
</tr>
<tr>
<td style="vertical-align: top;">London, United Kingdom, N16 8DH<br>
</td>
<td style="vertical-align: top;">Email:<br>
</td>
<td style="vertical-align: top;"><a name="howardcohtech.com"
target="mailto:howard@cohtech.com" href="mailto:howard@cohtech.com"></a><a class="moz-txt-link-abbreviated" href="mailto:howard@cohtech.com">howard@cohtech.com</a><br>
</td>
</tr>
</tbody>
</table>
<br>
</div>
<DIV><P><HR>
This message contains confidential information and is intended only<BR>
for the individual named. If you are not the named addressee you<BR>
should not disseminate, distribute or copy this e-mail. Please<BR>
notify the sender immediately by e-mail if you have received this<BR>
e-mail by mistake and delete this e-mail from you system.<BR>
<BR>
E-mail transmission cannot be guarenteed to be secure or error-free<BR>
as information could be intercepted, corrupted, lost, destroyed,<BR>
arrive late or incomplete, or contain viruses. The sender therefore<BR>
does not accept liability for any errors or omissions in the contents<BR>
of this message which arise as a result of e-mail transmission. If<BR>
verification is required please request a hard-copy version.
</P></DIV>
</body>
</html>