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

RE: Don't patch perlopentut: rewrite it completely

Thread Previous | Thread Next
February 17, 2013 06:08
RE: Don't patch perlopentut: rewrite it completely
Message ID:
> From: Tom Christiansen
> The perlopentut manpage is trying to be something else than certain
> people seem to want.  Just look at its horrible outline:


> Nearly every one of those is non-simple. That is not a 
> tutorial, and it is not
> just about open.  It is more like "FMTEYEWTK About open() and 
> I/O in Perl". If

fully agree...

>      *  No more one- or two-argument open.
>      *  No more tricks.
>      *  No more reopening STDIN or STDOUT.
>      *  No more trying to teach <>.
>      *  No more magic ARGV.  
>      *  No more magic minus.
>      *  No more dup or dup2.
>      *  No more sockets.
>      *  No more forks.
>      *  No more globs.
>      *  No more symbol table games.
>      *  No more read-write on text files; too hard; see FAQ.
>      *  No more file locking; too hard; see FAQ.

* no more IO Layers section, fortunately.

BTW I see factual error - 

" In Perl 5.8.0 a new I/O framework called "PerlIO" was introduced."
it was introduced in 5.6.0, or may be earlier...

I don't see this section in 5.6.1's perlopentut (obviously).

This factual error was added later in consequent modernizations.

> Here's one idea in that direction; it's just a sketch, but 
> the final version should not be much more complicated.  I'm
> still undecided about sysopen: should it stay or should it go?

wow..... seriously cool!  :)
I like it,

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About