perl5160delta: new xs bug fix section

diff --git a/Porting/perl5160delta.pod b/Porting/perl5160delta.pod
index 68d941e..bc11968 100644 (file)
--- a/Porting/perl5160delta.pod
+++ b/Porting/perl5160delta.pod
@@ -2930,6 +2930,40 @@ variable [perl #98662].
 
 =back
 
+=head2 Fixes affecting the C API
+
+=over
+
+=item *
+
+The C<newHVhv> XS function now works on tied hashes, instead of crashing or
+returning an empty hash.
+
+=item *
+
+The C<SvIsCOW> C macro now returns false for read-only copies of typeglobs,
+such as those created by:
+
+  $hash{elem} = *foo;
+  Hash::Util::lock_value %hash, 'elem';
+
+It used to return true.
+
+=item *
+
+The C<SvPVutf8> C function no longer tries to modify its argument,
+resulting in errors [perl #108994].
+
+=item *
+
+C<SvPVutf8> now works properly with magical variables.
+
+=item *
+
+C<SvPVbyte> now works properly non-PVs.
+
+=back
+
 =head2 Other notable fixes
 
 =over
@@ -2951,13 +2985,6 @@ recommendations.  See L<perlfunc/quotemeta> for details.
 
 =item *
 
-C<newHVhv> and tied hashes
-
-The C<newHVhv> XS function now works on tied hashes, instead of crashing or
-returning an empty hash.
-
-=item *
-
 No warning for C<open(foo::bar)>
 
 When one writes C<open foo || die>, which used to work in Perl 4, a
@@ -3259,16 +3286,6 @@ subsequently compiled code to become tainted [perl #64804].
 
 =item *
 
-The C<SvIsCOW> C macro now returns false for read-only copies of typeglobs,
-such as those created by:
-
-  $hash{elem} = *foo;
-  Hash::Util::lock_value %hash, 'elem';
-
-It used to return true.
-
-=item *
-
 Assignment to C<$^A> (the format output accumulator) now recalculates
 the number of lines output.
 
@@ -3406,19 +3423,6 @@ worrying about warnings.
 
 =item *
 
-The C<SvPVutf8> C function no longer tries to modify its argument,
-resulting in errors [perl #108994].
-
-=item *
-
-C<SvPVutf8> now works properly with magical variables.
-
-=item *
-
-C<SvPVbyte> now works properly non-PVs.
-
-=item *
-
 C<< $$ >> is no longer tainted.  Since this value comes directly from
 C<< getpid() >>, it is always safe.