Re: PATCH perl_reference.pod "Remedies for Inner Subroutines"

Stas Bekman <[EMAIL PROTECTED]> writes: > Brian McCauley wrote: > > > > Stas Bekman <[EMAIL PROTECTED]> writes: > >> > >>I think it would be more clear if all are declared at the top of the > >>file, > > > > Declaring variables a

Re: PATCH perl_reference.pod "Remedies for Inner Subroutines"

Stas Bekman <[EMAIL PROTECTED]> writes: > Brian McCauley wrote: > > > Here's a _very_ rough first cut at perl_reference.pod. I haven't even > > proof-read it yet so it's probably got spelling a and grammar errors > > but I just want to be sure I'

PATCH perl_reference.pod "Remedies for Inner Subroutines"

Stas Bekman <[EMAIL PROTECTED]> writes: > Brian McCauley wrote: > > > I think porting.pod is done. > > Indeed. > > > Now I have to attack perl_reference.pod, > > and I assume from what you said before you don't want to release the > > one witho

Re: PATCH porting.pod "First Mystery"

Stas Bekman <[EMAIL PROTECTED]> writes: > >... I'd keep the "for which" > > even if some people consider such strict English grammar to be > > affected. > > I guess it reads better if using commas: > > The easiest and the fastest way to solve the nested subrou

Re: PATCH porting.pod "First Mystery"

Stas Bekman <[EMAIL PROTECTED]> writes: > Brian McCauley wrote: > > Stas Bekman <[EMAIL PROTECTED]> writes: > > > >>- move the perl4 lib solution to the perl_reference.pod > > Will do when I get round to that bit. I still think a mention of it > &

Re: PATCH porting.pod "First Mystery"

Stas Bekman <[EMAIL PROTECTED]> writes: > - move the perl4 lib solution to the perl_reference.pod Will do when I get round to that bit. I still think a mention of it is needed in porting.pod to warn people away from it. If you disagree simply delete the offending paragraph. > - suggest turning