summaryrefslogtreecommitdiff
path: root/pod/perlvar.pod
Commit message (Collapse)AuthorAgeFilesLines
* remove the warning added for 5.16 and indicate the count is chars not bytesTony Cook2012-12-091-8/+1
|
* Deprecate lexical $_Father Chrysostomos2012-12-041-1/+2
| | | | | | | See tickets #114020 and #75598 for why. The changes to tests in cpan/Text-Tabs have been submitted upstream at rt.cpan.org #81698.
* Update docs to concur with $`,$&,$' changesFather Chrysostomos2012-11-271-10/+22
| | | | plus a couple of other pod tweaks.
* perlvar: two spaces after dotsFather Chrysostomos2012-11-121-6/+6
|
* Documentation of non-handle IO::Handle methods in perlvar.podTom Wyant2012-11-121-5/+20
| | | | | | | | | | The documentation to IO::Handle says that certain methods may not be set on file handles, only statically. It would be nice (in my perhaps not-so-humble opinion) if the distinction between per-filehandle and non-perl-filehandle methods were recognized in perlvar.pod. The appended universal diff is my cut at this. diff a/pod/perlvar.pod b/pod/perlvar.pod
* perlvar.pod: Document UTF8CACHEKarl Williamson2012-09-261-1/+3
|
* ${^LAST_FH}Father Chrysostomos2012-09-171-0/+11
| | | | | | | This was brought up in ticket #96672. This variable gives access to the last-read filehandle that Perl uses when it appends ", <STDIN> line 1" to a warning or error message.
* perlvar.pod, line 1337, bad filehandleJoaquin Ferrero2012-08-141-1/+1
|
* [perl #114020] perlvar: warn against my $_Father Chrysostomos2012-08-011-3/+9
|
* perlvar: Document all uses of implicit $_Father Chrysostomos2012-08-011-4/+6
|
* perlvar: Correct $^S’s descriptionFather Chrysostomos2012-07-291-2/+6
|
* perlvar: #109408Brian Fraser2012-06-271-38/+38
|
* Fixed repeated wordsWalt Mankowski2012-06-221-1/+1
|
* Clarify VMS-specific handling of $/ = \N.Craig A. Berry2012-03-251-6/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the record read feature was introduced in 5b2b9c687790241e8 in 1998 (but by Dan Sugalski, not Hans Mulder as the git history erroneously says), sysread() was a couple of years from learning about utf-8 and PerlIO was just a fancy way of calling stdio. The documentation was reasonable given that environment. Now it's potentially misleading to say that record reads are "the equivalent of C<sysread>" because sysread on filehandles opened with ":utf8" does characters, not bytes. The salient point about the analogy with sysread was always that the read is unbuffered. In the old days, this was in contrast to the buffering done in stdio's fread(), but now it's in contrast to the buffering in the perlio layer. By emphasizing the role of buffering, we can actually shorten and simplify the docs. Side note: Both Camel 3 and Camel 4 have the following problematic statement in the documentation of $/: "Record mode mixes with line mode only on systems where standard I/O supplies a read(3) function; VMS is a notable exception." VMS certainly does have a read(3) function and in fact that's what's used directly for record reads (via PerlLIO_read) on VMS only. And as far as I know, it is fread(), not read(), that is considered "standard I/O" everywhere. N.B. Record reads on non-record-oriented files on VMS will likely start using the same buffering as other platforms in a future version of Perl.
* [rt #79960] document how broken $/ = \N is for unicode streamsTony Cook2012-03-231-0/+7
| | | | | | It's kind of late in the release process to change how $/ = \N works for unicode streams, briefly document how broken it is and let the user know it may change.
* perlvar: Fix long linesFather Chrysostomos2012-03-071-132/+140
| | | | | Also, make all indented code start with a four-space indent. Before this it was inconsistent throughout.
* Dear perlvar: ${^WARNING_BITS} was added in 5.6Father Chrysostomos2012-03-071-1/+1
|
* perlvar: Document ${^WARNING_BITS} betterFather Chrysostomos2012-03-071-1/+3
| | | | | | | | Don’t refer people to warnings.pm for more information, as it contains no more information about this variable. Explain the scoping and also mention that the values are considered internal.
* perlvar: $] is not deprecatedFather Chrysostomos2012-02-181-2/+0
| | | | See <20011022034838.B1676@blackrider> and commit 0c8d858bc.
* Further eliminate POSIX-emulation under LinuxThreadsÆvar Arnfjörð Bjarmason2012-02-151-5/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Under POSIX threads the getpid() and getppid() functions return the same values across multiple threads, i.e. threads don't have their own PID's. This is not the case under the obsolete LinuxThreads where each thread has a different PID, so getpid() and getppid() will return different values across threads. Ever since the first perl 5.0 we've returned POSIX-consistent semantics for $$, until v5.14.0-251-g0e21945 when the getpid() cache was removed. In 5.8.1 Rafael added further explicit POSIX emulation in perl-5.8.0-133-g4d76a34 [1] by explicitly caching getppid(), so that multiple threads would always return the same value. I don't think all this effort to emulate POSIX sematics is worth it. I think $$ and getppid() are OS-level functions that should always return the same as their C equivalents. I shouldn't have to use a module like Linux::Pid to get the OS version of the return values. This is pretty much a complete non-issue in practice these days, LinuxThreads was a Linux 2.4 thread implementation that nobody maintains anymore[2], all modern Linux distros use NPTL threads which don't suffer from this discrepancy. Debian GNU/kFreeBSD does use LinuxThreads in the 6.0 release, but they too will be moving away from it in future releases, and really, nobody uses Debian GNU/kFreeBSD anyway. This caching makes it unnecessarily tedious to fork an embedded Perl interpreter. When someone that constructs an embedded perl interpreter and forks their application, the fork(2) system call isn't going to run Perl_pp_fork(), and thus the return value of $$ and getppid() doesn't reflect the current process. See [3] for a bug in uWSGI related to this, and Perl::AfterFork on the CPAN for XS code that you need to run after forking a PerlInterpreter unbeknownst to perl. We've already been failing the tests in t/op/getpid.t on these Linux systems that nobody apparently uses, the Debian GNU/kFreeBSD users did notice and filed #96270, this patch fixes that failure by changing the tests to test for different behavior under LinuxThreads, I've tested that this works on my Debian GNU/kFreeBSD 6.0.4 virtual machine. If this change is found to be unacceptable (i.e. we want to continue to emulate POSIX thread semantics for the sake of LinuxThreads) we also need to revert v5.14.0-251-g0e21945, because currently we're only emulating POSIX semantics for getppid(), not getpid(). But I don't think we should do that, both v5.14.0-251-g0e21945 and this commit are awesome. This commit includes a change to embedvar.h made by "make regen_headers". 1. http://www.nntp.perl.org/group/perl.perl5.porters/2002/08/msg64603.html 2. http://pauillac.inria.fr/~xleroy/linuxthreads/ 3. http://projects.unbit.it/uwsgi/ticket/85
* clarify how $SIG{__DIE__} can returnDavid Mitchell2012-01-081-4/+4
| | | | | | | It can return via 'goto &sub', but not via 'goto LABEL'. The docs originally just said 'via goto' See [perl #44367].
* Mention evalbytes in perlvar as a (_) functionFather Chrysostomos2011-12-161-1/+2
|
* perlvar: Don’t mention 5.9Father Chrysostomos2011-12-161-1/+1
|
* perlvar: Consistent use of spaces after dotsFather Chrysostomos2011-12-161-246/+254
| | | | | | | | | | | This commit changes it to use two spaces, for several reasons. It was already inconsistent. Although it used one space in most cases, the rest of Perl’s documentation uses two. pod2man expects two spaces, as it adds two spaces for sentences ending at the end of a line in the middle of a paragraph, as it was designed to work with Perl’s origi- nal pod docs, which used two spaces. If this document used one space throughout, one would have to go through it and make sure no sentences end at the ends of lines except at the end of a paragraph.
* perlvar: document what $[ will do under use v5.16Father Chrysostomos2011-12-151-0/+4
|
* Reimplement $[ as a moduleFather Chrysostomos2011-10-211-8/+19
| | | | | | | | | | | | | | | | | This commit reimplements $[ using PL_check hooks, custom pp func- tions and ties. Outside of its compile-time use, $[ is now parsed as a simple varia- ble, so function calls like foo($[) are permitted, which was not the case with the former implementation removed by e1dccc0. I consider that a bug fix. The ‘That use of $[ is unsupported’ errors are out of necessity deferred to run-time and implemented by a tied $[. Indices between 0 and the array base are now treated consistently, as are indices between a negative array base and zero. That, too, is a bug fix.
* Corrected: 'filehanlde' => 'filehandle'Alan Haggai Alavi2011-10-111-1/+1
| | | | Signed-off-by: David Golden <dagolden@cpan.org>
* Add missing C on </p> constructDave Rolsky2011-09-281-3/+3
|
* Make a new section for vars related to interpreter stateDave Rolsky2011-09-281-312/+320
| | | | | | | This is a little arbitrary, for example one could argue that @INC and %INC belong in there. My main goal was to move stuff that you're less likely to care about later in the document. Basically, this is the stuff that wizards care about and mere mortals generally don't.
* Move $0 and $$ togetherDave Rolsky2011-09-281-48/+48
|
* Move uid & gid variable docs next to each otherDave Rolsky2011-09-281-35/+35
|
* Dear perlvar: ${PEN} was introduced in 5.8.0.Father Chrysostomos2011-09-151-1/+1
|
* document convention for keys in %^HZefram2011-09-151-0/+6
|
* remove index offsetting ($[)Zefram2011-09-091-16/+8
| | | | | | $[ remains as a variable. It no longer has compile-time magic. At runtime, it always reads as zero, accepts a write of zero, but dies on writing any other value.
* Doc update for changes in 5.15.0 + tweaksFather Chrysostomos2011-06-171-2/+3
|
* perlvar.pod: fixed typoAlan Haggai Alavi2011-06-111-1/+1
| | | | Signed-off-by: David Golden <dagolden@cpan.org>
* [perl #91614] Suggestion for improving documentation of $!John P. Linderman2011-05-251-15/+18
| | | | | | | | | | | | | | | | | | While trying to understand a bug report at http://www.perlmonks.org/?node_id=906466 I realized that the documentation for $! was not crystal clear. For example If used numerically, yields the current value of the C C<errno> variable, or in other words, if a system or library call fails, it sets this variable. That's not "in other words", these are totally different concepts. And it isn't clear whether this variable refers to errno or $! (I assumed the latter, and was wrong, as Devel::Peek demonstrated). And $! cannot be undef, as asserted (later), because errno always contains a value, however irrelevant.
* perlvar: Fix broken linksKarl Williamson2011-05-191-4/+4
|
* [perl #90306] Fix simple typosMarcel Grünauer2011-05-191-1/+1
|
* Fix bad pod links found by Test::Pod::LinkCheckApocalypse2011-02-151-1/+1
|
* [perl #81584] recommend Devel::FindAmpersandFather Chrysostomos2011-01-161-1/+2
|
* Restore the old description of $[Father Chrysostomos2011-01-021-5/+13
| | | | | | | | | The new entry is a bit too futuristic: assignment to $[ still works and it is not read-only. This does not fully restore the old description, as it contained grammatical errors and parts of it were not updated when 5.10 changed the scoping.
* Fix typo in perlvarChris 'BinGOs' Williams2010-12-161-1/+1
|
* [perl #79914] documentation bug in perldoc perlvar $|Lukas Mai2010-11-281-1/+1
|
* Add an index entry for ${^GLOBAL_PHASE}Florian Ragwitz2010-11-141-0/+1
|
* Users don't normally care about the blead releasesFlorian Ragwitz2010-11-141-1/+1
|
* There are no values not mentioned hereFlorian Ragwitz2010-11-141-1/+1
|
* add example for ${^GLOBAL_PHASE} and description to perlmodChas. J. Owens IV2010-11-141-2/+43
| | | | | Signed-off-by: Florian Ragwitz <rafl@debian.org> [rafl@debian.org: Minor rewording based on input from TIMB]
* Whitespace fixes to perlvarbriandfoy/perlvarbrian d foy2010-11-011-3/+3
|
* Added ${^GLOBAL_PHASE} to perlvarbrian d foy2010-11-011-0/+64
|
View Lorry Controller Status