Document calling convention for Perl_mro_register

I had to look in embed.fnc to find this out when I wanted to use it.

2 files changed, 10 insertions, 1 deletions

diff --git a/mro.c b/mro.c
index 386f898984..e0ab5bc96c 100644
--- a/mro.c
+++ b/mro.c
@@ -114,6 +114,11 @@ Perl_mro_get_from_name(pTHX_ SV *name) {
     return INT2PTR(const struct mro_alg *, SvUVX(*data));
 }
 
+/*
+=for apidoc mro_register
+Registers a custom mro plugin.  See L<perlmroapi> for details.
+*/
+
 void
 Perl_mro_register(pTHX_ const struct mro_alg *mro) {
     SV *wrapper = newSVuv(PTR2UV(mro));
diff --git a/pod/perlmroapi.pod b/pod/perlmroapi.pod
index 74bd9b2a77..54da7dded2 100644
--- a/pod/perlmroapi.pod
+++ b/pod/perlmroapi.pod
@@ -9,7 +9,7 @@ resolution orders other than the default (linear depth first search).
 The C3 method resolution order added in 5.10.0 has been re-implemented as
 a plugin, without changing its Perl-space interface.
 
-Each plugin should register itself with C<Perl_mro_register> by providing
+Each plugin should register itself by providing
 the following structure
 
     struct mro_alg {
@@ -20,6 +20,10 @@ the following structure
         U32 hash;
     };
 
+and calling C<Perl_mro_register>:
+
+    Perl_mro_register(aTHX_ &my_mro_alg);
+
 =over 4
 
 =item resolve