summaryrefslogtreecommitdiff
path: root/pod/perltodo.pod
diff options
context:
space:
mode:
authorDavid Golden <dagolden@cpan.org>2009-10-06 16:02:53 -0400
committerDavid Golden <dagolden@cpan.org>2009-10-06 16:02:53 -0400
commit5b7d14ffe3988c7f70fd9dc76be9c44168d17a62 (patch)
tree4d3d637cec13c23214b8f4112d85d881adf726bc /pod/perltodo.pod
parente851c10581f8b45e99ba164a13a07381402b7e64 (diff)
downloadperl-5b7d14ffe3988c7f70fd9dc76be9c44168d17a62.tar.gz
Expand on cookbook todo
Diffstat (limited to 'pod/perltodo.pod')
-rw-r--r--pod/perltodo.pod10
1 files changed, 10 insertions, 0 deletions
diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index b17ad9f5b0..35193193ba 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -577,6 +577,16 @@ extracted from perlguts.) The target audience should be XS novices, who need
more examples than perlguts but something less overwhelming than perlapi.
Recipes should provide "one pretty good way to do it" instead of TIMTOWTDI.
+Rather than focusing on interfacing Perl to C libraries, such a cookbook
+should probably focus on how to optimize Perl routines by re-writing them
+in XS. This will likely be more motivating to those who mostly work in
+Perl but are looking to take the next step into XS.
+
+Deconstructing and explaining some simpler XS modules could be one way to
+bootstrap a cookbook. (List::Util? Class::XSAccessor? Tree::Ternary_XS?)
+Another option could be deconstructing the implementation of some simpler
+functions in op.c.
+
=head2 Remove the use of SVs as temporaries in dump.c
F<dump.c> contains debugging routines to dump out the contains of perl data