On 2007-05-22, at 10:49:27 +0200, Marcus Holland-Moritz wrote:

>  On 2007-05-22, at 09:16:01 +0100, Steve Hay wrote:
>  
>  > If so, exactly what needs to happen to 
>  > get them into Devel::PPPort? Is it just a matter of adding the 
>  > appropriate "=for apidoc" chunks and then Marcus does the rest when a 
>  > new release of Devel-PPPort is made?
>  
>  Hehe, yes, that would be the easy (for you ;-) way!
>  
>  Another way would be to send me a patch for D::PPP.
>  
>  The third -- and best -- way would be to do both. :-)
>  
>  But for now, I think it would be the best idea to start
>  with documenting the SvPV_ stuff in sv.h. Currently, of
>  the 23 SvPV_ macros, only 5 are documented, all of which
>  are flagged as members of the public API:
>  
>            SvPV_const
>            SvPV_flags
>            SvPV_flags_const
>            SvPV_flags_const_nolen
>            SvPV_flags_mutable
>    DOC PUB SvPV_force
>            SvPV_force_flags
>            SvPV_force_flags_mutable
>            SvPV_force_flags_nolen
>            SvPV_force_mutable
>            SvPV_force_nolen
>    DOC PUB SvPV_force_nomg
>            SvPV_force_nomg_nolen
>            SvPV_free
>            SvPV_mutable
>    DOC PUB SvPV_nolen
>            SvPV_nolen_const
>    DOC PUB SvPV_nomg
>            SvPV_nomg_const
>            SvPV_nomg_const_nolen
>            SvPV_renew
>    DOC PUB SvPV_set
>            SvPV_shrink_to_cur
>  
>  At least all of the macros that are supposed to be public
>  should also be documented.
>  
>  I'll have a look at which of them can easily be drawn into
>  D::PPP in parallel.

I think I've added most of the above with Devel-PPPort 3.11_02.

Marcus

-- 
travel, n.:
	Something that makes you feel like you're getting somewhere.