summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2000-03-22 15:02:59 +0000
committerGurusamy Sarathy <gsar@cpan.org>2000-03-22 15:02:59 +0000
commit4bca7e4f54e1629a267f78a6411de31fe29da1d8 (patch)
treefa9d2edb60918364e1176da0e0bb59fa6caf6e5f
parent97017a809da405a36dfccf88d7bd13d26ca0e932 (diff)
downloadperl-4bca7e4f54e1629a267f78a6411de31fe29da1d8.tar.gz
missing pieces in perldelta
p4raw-id: //depot/perl@5876
-rw-r--r--pod/perldelta.pod23
1 files changed, 18 insertions, 5 deletions
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 4ad600210d..df1e68d56e 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -661,8 +661,10 @@ of the traditional two-argument form. See L<perlfunc/open>.
=head2 64-bit support
- NOTE: The Configure flags -Duselonglong and -Duse64bits have been
- deprecated. Use -Duse64bitint instead.
+ WARNING: 64-bit support is still experimental on most platforms.
+ Existing support only covers the LP64 data model. In particular, the
+ LLP64 data model is not yet supported. 64-bit libraries and system
+ APIs on many platforms have not stabilized--your mileage may vary.
Any platform that has 64-bit integers either
@@ -672,6 +674,9 @@ Any platform that has 64-bit integers either
are able to use "quads" (64-bit integers) as follows:
+ NOTE: The Configure flags -Duselonglong and -Duse64bits have been
+ deprecated. Use -Duse64bitint instead.
+
=over 4
=item *
@@ -716,7 +721,7 @@ and compile Perl using the -Duse64bitint Configure flag.
There are actually two modes of 64-bitness: the first one is achieved
using Configure -Duse64bitint and the second one using Configure
-Duse64bitall. The difference is that the first one is minimal and
-the second one maximal.
+the second one maximal. The first works in more places than the second.
The C<use64bitint> does only as much as is required to get 64-bit
integers into Perl (this may mean, for example, using "long longs")
@@ -1054,6 +1059,10 @@ array element in that slot.
=head2 Pseudo-hashes work better
+ WARNING: The pseudo-hash data type continues to be experimental.
+ Limiting oneself to the interface elements provided by the
+ fields pragma will provide protection from any future changes.
+
Dereferencing some types of reference values in a pseudo-hash,
such as C<< $ph->{foo}[1] >>, was accidentally disallowed. This has
been corrected.
@@ -2712,7 +2721,7 @@ operation must be considered erroneous. For example:
These expressions will get run-time errors in some future release of
Perl.
-=head2 Many features still experimental
+=head2 Experimental features
As discussed above, many features are still experimental. Interfaces and
implementation of these features are subject to change, and in extreme cases,
@@ -2725,14 +2734,18 @@ include the following:
=item Unicode
+=item 64-bit support
+
=item Lvalue subroutines
=item Weak references
-=item File globbing now implemented internally
+=item The pseudo-hash data type
=item The Compiler suite
+=item Internal implementation of file globbing
+
=item The DB module
=item The regular expression constructs C<(?{ code })> and C<(??{ code })>