From 3d0ae7ba72551d8af1ecbcfb8a67d9a77f1cf195 Mon Sep 17 00:00:00 2001
From: Gurusamy Sarathy <gsar@cpan.org>
Date: Sun, 7 May 2000 01:22:23 +0000
Subject: avoid warnings in diagnostics.pm; pod tweaks (from Peter Prymmer and
 Tom Phoenix)

p4raw-id: //depot/perl@6077
---
 pod/perlrun.pod | 12 ++++++++++++
 pod/perltie.pod |  7 ++-----
 2 files changed, 14 insertions(+), 5 deletions(-)

(limited to 'pod')

diff --git a/pod/perlrun.pod b/pod/perlrun.pod
index f1e2c9a62e..e105b00a7a 100644
--- a/pod/perlrun.pod
+++ b/pod/perlrun.pod
@@ -809,6 +809,18 @@ Relevant only if your perl executable was built with B<-DDEBUGGING>,
 this controls the behavior of global destruction of objects and other
 references.
 
+=item PERL_ROOT (specific to the VMS port)
+
+A translation concealed rooted logical name that contains perl and the
+logical device for the @INC path on VMS only.  Other logical names that
+affect perl on VMS include PERLSHR, PERL_ENV_TABLES, and 
+SYS$TIMEZONE_DIFFERENTIAL but are optional and discussed further in 
+L<perlvms> and in F<README.vms> in the Perl source distribution.
+
+=item SYS$LOGIN (specific to the VMS port)
+
+Used if chdir has no argument and HOME and LOGDIR are not set.
+
 =back
 
 Perl also has environment variables that control how Perl handles data
diff --git a/pod/perltie.pod b/pod/perltie.pod
index c835738573..95de3bb928 100644
--- a/pod/perltie.pod
+++ b/pod/perltie.pod
@@ -862,14 +862,11 @@ called:
 =head1 SEE ALSO
 
 See L<DB_File> or L<Config> for some interesting tie() implementations.
+A good starting point for many tie() implementations is with one of the
+modules L<Tie::Scalar>, L<Tie::Array>, L<Tie::Hash>, or L<Tie::Handle>.
 
 =head1 BUGS
 
-Tied arrays are I<incomplete>.  They are also distinctly lacking something
-for the C<$#ARRAY> access (which is hard, as it's an lvalue), as well as
-the other obvious array functions, like push(), pop(), shift(), unshift(),
-and splice().
-
 You cannot easily tie a multilevel data structure (such as a hash of
 hashes) to a dbm file.  The first problem is that all but GDBM and
 Berkeley DB have size limitations, but beyond that, you also have problems
-- 
cgit v1.2.1


From 277ddfaf09c11f4f38a1c6f63c004bfe4d066e3d Mon Sep 17 00:00:00 2001
From: Gurusamy Sarathy <gsar@cpan.org>
Date: Sun, 7 May 2000 05:24:46 +0000
Subject: note about undocumented caller() return value (from M.J.T. Guy); yet
 another peek.t tweak

p4raw-id: //depot/perl@6083
---
 pod/perlfunc.pod | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'pod')

diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 8e66e1b5f8..4e67506e26 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -539,9 +539,10 @@ Here $subroutine may be C<(eval)> if the frame is not a subroutine
 call, but an C<eval>.  In such a case additional elements $evaltext and
 C<$is_require> are set: C<$is_require> is true if the frame is created by a
 C<require> or C<use> statement, $evaltext contains the text of the
-C<eval EXPR> statement.  In particular, for a C<eval BLOCK> statement,
+C<eval EXPR> statement.  In particular, for an C<eval BLOCK> statement,
 $filename is C<(eval)>, but $evaltext is undefined.  (Note also that
 each C<use> statement creates a C<require> frame inside an C<eval EXPR>)
+frame.  C<$hasargs> is true if a new instance of C<@_> was set up for the
 frame.  C<$hints> and C<$bitmask> contain pragmatic hints that the caller
 was compiled with.  The C<$hints> and C<$bitmask> values are subject to
 change between versions of Perl, and are not meant for external use.
-- 
cgit v1.2.1