Front page | perl.perl5.porters |
Postings from January 2012
Re: typemap documentation
Thread Previous
|
Thread Next
From:
David Mertens
Date:
January 16, 2012 11:36
Subject:
Re: typemap documentation
Message ID:
CA+4ieYUisx4MLDvwDEixxiLm=oZjHJid=mKTDhva1E+D331cSw@mail.gmail.com
T_OPAQUE => Documented, tested, but the docs are slightly opaque? ;)
Hilarious!
Do you have a timeline in mind? Should I work on this tonight, or can it
wait for this weekend?
David
On Mon, Jan 16, 2012 at 1:04 PM, Steffen Mueller <smueller@cpan.org> wrote:
> Hi Nicholas, hi all,
>
> TODO list of undocumented/untested typemaps attached.
>
>
> On 01/16/2012 06:21 PM, Nicholas Clark wrote:
>
>> On Mon, Jan 16, 2012 at 08:45:43AM +0100, Steffen Mueller wrote:
>>
>>> would anybody oppose if I tried to get the existing documentation on the
>>> core typemaps updated and into a manpage like perlxstypemap or so (with
>>> the appropriate pointers from perlxs)? We have quite a bit of docs on
>>>
>>
>> You make it awkward for me to not object. Although, arguably this is
>> sensible on your part, as you assume that silence is approval, and this
>> way
>> you can be confident to get hundreds of subscribers to the list approving
>> your idea :-)
>>
>
> Well, the alternative would have been to just do it without mentioning it
> on list or just asking after I'm done. Asking for permission in a
> non-assertive way in these parts is not helping anybody, is it?
>
>
> On Mon, Jan 16, 2012 at 05:52:28PM +0100, Steffen Mueller wrote:
>>
>>> 3) Implement whatever to make sure we get perlxstypemaps.pod and man.
>>>
>>
>> I believe now that all is needed for plain files that contain Pod, is to
>> add the correct data into pod/perl.pod and then run perl Porting/
>> pod_rules.pl
>> to regenerate things.
>>
>> For files in pod/ "correct data" is just the line in the table of
>> contents. For pods outside of pod/ (so far, only dual life Pods), you also
>> need to add a "path" line in the bit between =begin buildtoc and
>> =end buildtoc
>>
>
> Very nice!
>
>
> I could use help with all three of these and particularly part 1) is
>>> easily parallelizable!
>>>
>>
>> I doubt I have time for anything other than moral support.
>>
>
> The above was already useful!
>
> --Steffen
>
--
Sent via my carrier pigeon.
Thread Previous
|
Thread Next