Re: authorial perlipc edit

2010-11-09 Thread demerphq
On 9 November 2010 15:44, Tom Christiansen wrote: > On 09 Nov 2010 06:02:55 GMT you wrote: > >>> For now, I'm sending the complete revision in toto. > >> Applied as cf21866, with some tpyo corretcions. > > Thanks very muhc.  I think it's a better document now, > even if only marginally. > > ==

Re: authorial perlipc edit

2010-11-09 Thread demerphq
On 9 November 2010 19:24, Jesse Vincent wrote: > > > > On Tue, Nov 09, 2010 at 11:20:51AM -0700, Tom Christiansen wrote: >> > Ultimately it's your call, but I think the Cookbook references should >> > be in there. >> >> Thanks, Brian. >> >> I still feel that I must recuse myself from making that c

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-03 Thread demerphq
On 3 December 2010 13:49, Shlomi Fish wrote: > Hi all, > > after I posted my series of patches to perlipc.pod , I saw that tchrist posted > his version, which got accepted immediately. As a downside to that, I'll have > to restart my work. However, I noticed that perlipc.pod still has many > perce

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-03 Thread demerphq
On 3 December 2010 14:43, Shlomi Fish wrote: > On Friday 03 December 2010 15:25:14 demerphq wrote: >> On 3 December 2010 13:49, Shlomi Fish wrote: >> > Hi all, >> > >> > after I posted my series of patches to perlipc.pod , I saw that tchrist >>

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-04 Thread demerphq
On 4 December 2010 15:18, Abigail wrote: > On Fri, Dec 03, 2010 at 05:08:42PM -0800, chromatic wrote: >> On Friday 03 December 2010 at 16:53, Leon Timmermans wrote: >> >> > We do, honestly. I'm tired of having to explain to newbies why the >> > official perl documentation is not strict friendly, w

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-04 Thread demerphq
On 4 December 2010 16:29, Tom Christiansen wrote: > Yves wrote: > >> Well, that is not entirely correct. Some /are/ full blown programs. > > *Those* I do try to always my() or our() or state() or sometimes > even local(), which is indeed appropriate in places: > >    use Carp qw< :DEFAULT cluck >;

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-04 Thread demerphq
On 4 December 2010 17:43, Tom Christiansen wrote: >> I think we would both agree that that is way to much. And I >> automatically assume code with "use utf8" in it is subtly >> broken until proved otherwise anyway. :-) > > Oh drat!  That's distressing.  I some time ago reached the conclusion > tha

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-06 Thread demerphq
On 5 December 2010 07:54, Naveed Massjouni wrote: > This thread is really depressing.  Personally, I like all of Shlomi's > suggestions.  I can't fathom why bareword global filehandles are still > pervasive in the perl docs.  But instead of the community getting to > discuss the merits of the chan

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-06 Thread demerphq
On 6 December 2010 19:25, Tom Christiansen wrote: > This witch-hunt is counter-productive and harmful.  You should not > be offended, or even surprised, if its results are not agreed to. Tom, using terms like "witch-hunt" is not fair - it implies there is malice intent on Shlomi's behalf which I

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-06 Thread demerphq
On 6 December 2010 19:01, Shlomi Fish wrote: > Hi Yves, > > On Monday 06 December 2010 10:42:23 demerphq wrote: >> On 5 December 2010 07:54, Naveed Massjouni wrote: >> > This thread is really depressing.  Personally, I like all of Shlomi's >> > suggestion