nor -Duse64bitall.
Last but not least: note that due to Perl's habit of always using
-floating point numbers the quads are still not true integers.
+floating point numbers, the quads are still not true integers.
When quads overflow their limits (0...18_446_744_073_709_551_615 unsigned,
-9_223_372_036_854_775_808...9_223_372_036_854_775_807 signed), they
are silently promoted to floating point numbers, after which they will
constructs now generate a warning, since they may take on new
semantics in later versions of Perl.
+Many diagnostics now report the internal operation in which the warning
+was provoked, like so:
+
+ Use of uninitialized value in concatenation (.) at (eval 1) line 1.
+ Use of uninitialized value in print at (eval 1) line 1.
+
+Diagnostics that occur within eval may also report the file and line
+number where the eval is located, in addition to the eval sequence
+number and the line number within the evaluated text itself. For
+example:
+
+ Not enough arguments for scalar at (eval 4)[newlib/perl5db.pl:1411] line 2, at EOF
+
=head1 Performance enhancements
=head2 Simple sort() using { $a <=> $b } and the like are optimized
(F) Compile-time-substitutions (such as overloaded constants and
character names) were not correctly set up.
+=item CORE::%s is not a keyword
+
+(F) The CORE:: namespace is reserved for Perl keywords.
+
=item defined(@array) is deprecated
(D) defined() is not usually useful on arrays because it checks for an