develooper Front page | perl.perl5.porters | Postings from February 2013

Re: perlopentut modernization

Thread Previous
From:
Alexander Hartmaier
Date:
February 14, 2013 15:52
Subject:
Re: perlopentut modernization
Message ID:
CAB49QrZKa_bZLWHXPwz8BxODZJYN1X396+u_=PvwV0_Bu+_7LA@mail.gmail.com
On Thu, Feb 14, 2013 at 2:32 PM, Ricardo Signes
<perl.p5p@rjbs.manxome.org>wrote:

> * Alexander Hartmaier <alex.hartmaier@gmail.com> [2013-02-14T03:43:41]
> > On Thu, Feb 14, 2013 at 3:51 AM, Ricardo Signes
> > <perl.p5p@rjbs.manxome.org>wrote:
> >
> > > special variable C<$!>  -- should link to perlvar, since $! is a bit
> weird
> > >
> > I was thinking about even use-ing English and its $OS_ERROR  (or $ERRNO),
> > what do you think about that?
>
> I do not suggest it.
>
> > As demerhq already pointed out that's not something I've written but just
> > left in from the current doc. I not even knew that before I've started
> > working on the doc.
> >
> > As I don't want to advocate the two-arg open form I'd rather remove this
> > from the tutorial than including in a 2-arg open section where people
> might
> > start using it again because of this 'feature'.
>
> The point is not that you wrote every word of the text, but that you put
> the
> text into the state I quoted, and that this state is in error.
>
> I understand that if you are mentioning two-arg open only to point out
> that it
> exists, you may not want to emphasize this kind of feature.  Probably you
> should give it at least a few words, especially regarding space between the
> mode and the name.  This need not be there to present anything as a
> feature,
> but if the explanation is there to say "you might also see this form,"
> then it
> should include it as it may well be seen:  open FH, "< filename";
>
> --
> rjbs
>
I'll look into it.

Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About