On Fri, Jul 2, 2010 at 14:06, Leon Timmermans <faw...@gmail.com> wrote: > I'm in too. snip
Choose something from the short term goals list for now. snip > * Changing all uses of typeglob filehandles to lexical filehandles > (except where documenting open itself, obviously) > * Changing all uses of two argument open to three argument open > (except where documenting open itself) snip These are part of the long term goal of cleaning up the examples in the docs. The task itself is so large that my plan is to choose a specific set of docs (preferable the most used ones like perlfunc) to clean up for each release. snip > I would really like the object oriented documentation to be taken into > the current century. Pretty much all of it was written in the 90s and > it's grossly out of date. I don't want to see @ISA anymore, seriously. > Not to mention there are some bugs in there. Some of the current > documentation is so bad that I think deleting it right now even before > we've written a replacement would be an improvement. This would be a > rather serious amount of work, it should probably be done by a small > group of people instead of one person. snip Yeah, I am trying to save as much of the current documentation as possible (just to cut down on the workload), but somethings like the OO stuff and perlre are just going to need complete overhauls. snip > Other ideas: > * perltrap should include modern languages like Python, Ruby and PHP. > This would be a lot more useful than Perl4 and awk. > * perlmodinstall should be made Build.PL aware > * perlipc should use IO::* instead of low level functions snip This is all good stuff to be adding to our long term goals. snip > I wish I had as much time as I have ideas though :-| snip It took me a year to get perlopquick to the point it is in now. I figure it is going to take that long or longer for each of the other documents that need massive overhauling as well. I am going for a slow and steady approach. So long as we see some forward progress I will be happy. -- Chas. Owens wonkden.net The most important skill a programmer can have is the ability to read.
