From: Brian Ingerson [mailto:[EMAIL PROTECTED]]
>
> > 2) More detailed documentation for the bone-headed on best
> > practices when manipulating [AHIS]V's. Yes much of the
> > general stuff is in perlguts, perlapi, perlxs, etc.
> > But a coherent discussion of practical implementation
> > details would be most excellent. Checking for read-only
> > values, objects and references, magic, do's and don't's,
> > etc.
>
> Now your talkin'. This is a slam-dunk. We need better doc for sure. If
> you want to take the doc helm for a while, then I say "Aye-aye".
I will lend a hand where I can. But being pretty ignorant on the C side of
things makes me particularly blind in many areas of importance to Inline. If
sufficient hand-holding is available and time permits I'll try to do more
than make minor contributions.
> The best way to do this is through patches.
>
> 1) Get a copy of makepatch from CPAN
> 2) Get the latest Inline source.
> 3) Untar the source.
> 4) Make a complete copy of the whole directory.
> 5) Modify the copy anyway you wish.
> 6) Say 'makepatch Inline-0.31/ Inline-0.31.modified/ >
> Inline-0.31-patch'
> 7) Send me the patch.
makepatch downloaded, installed, and documentation in hand...
Have a good trip.
Garrett
