Questions about Perl and doc

[Julien ÉLIE]

En réponse à Russ Allbery :
> We could do it that way, but creating a real INN::* hierarchy of Perl
> modules would be useful if, say, we had a real Perl API to the
> configuration parsing interface, or a Perl API to the storage system
> (which could make some programs like cnfsstat much nicer), or a Perl API
> to the ctlinnd interface so that ctlinnd operations could be done
> natively.

All right.  That sounds, indeed, very good!


> I think that's a good idea, although innreport is an odd beast with a
> fairly unusual Perl style and probably could stand more surgery than
> that.

And there is also the problem of the proper accounting of checkpoints
which is not finished.
I do not know how to deal with that.  Do you think adding a log file
for innreport which contains the last checkpoint processed, if any, for
each peer would be good?  (It would allow to see what has already been
processed during the previous day.)  Or do you have a cleaner idea?


> But a little bit at a time.  :)

Sure!


> inn-intro pages for various man page sections that point
> to all of the available utilities and documentation sound like a great
> idea, though.

Then it would be better to reorganize doc/pod in subdirectories before
doing that.  But we need to find which subdirectories :)

-- 
Julien ÉLIE

« Tout va bien, pourvu que cela dure, comme disait Arlequin
  en tombant d'un cinquième étage. » (Prosper Mérimée)