Tasks that still need people:
* reading perlopquick descriptions for correctness and clarity (this
needs as many people as possible)
* discussion of the proposed items in the list (this needs as many
people as possible)
* work on the logo/mascot
* first draft about how to document documentation changes added to perlpolicy
* finding a way to have one document that creates both a <DOC>.pod
and <DOC>ref.pod
Current assignments list:
* Shawn H Corey: moving perlop stuff into perlopquick
* Bob Goolsby: fixing the metasyntactic variables in perlopquick
* John Anderson: adding <> to perlopquick and scanning for other
missed operators
* Fiachra O Donoghue: reading and testing the examples in perlopquick
* Karen Etheridge: reading perlopquick descriptions for correctness
and clarity
* Anirban Adhikary: first draft of the text that will go into perlfuncref
* Ashley Pond: first draft of the text that will go into perlopref
--
Chas. Owens
wonkden.net
The most important skill a programmer can have is the ability to read.
> * John Anderson: adding <> to perlopquick and scanning for other
> missed operators
So far, it looks like qr(X) and `X`/qx(X), were missed in the original conversion.
I'm planning on doing `X`/qx(X) during/after doing <>/<X>. (The stuff for that is sorted of mixed together with <>/<X> in perlop.pod, so it makes sense to me to do those at the same time.)
If somebody could grab qr(X) (or if Chas. could note it for later assignment) that would be good...
chrs,
john.
On Jul 2, 2010, at 1:10 PM, Chas. Owens wrote:
> * John Anderson: adding <> to perlopquick
I've committed a (very rough) draft of a <X> section to my fork -- see it at <http://github.com/genehack/perlopquick/commit/c55a7a83027e690ceea28e65a35dd6387b9d5460>. I haven't asked Chas. to pull yet because I'm not yet done, and I'd like to get some feedback before continuing further.
In particular, I'm interested in what people think of the way I've organized the "<FILEHANDLE>" versus "<FILEGLOB>" forms of "<X>" or whether it would be better have an explicit "=head2 <FILEHANDLE>" section followed by a "=head2 <NOT_A_FILEHANDLE>" (or something) section.
thanks,
john.