in reply to extracting information about xsubs

Check the docs :)

There is no way to get a list of xsubs, except to load a module and boot it ( see DynaLoader

Even then, that is all you can get unless you can provoke a croaking like wxperl_usage

You might be able to get a list of xsubs if you use a disassembler, something like objdump won't help as the only exported symbol is boot_Storable... which "registers" freeze/thaw/nstore/retrieve...

Replies are listed 'Best First'.
Re^2: extracting information about xsubs
by hurricup (Pilgrim) on Aug 19, 2015 at 03:58 UTC

    Well, this is not true. Names are in there, not hashed or smth. It means that you can extract them. Question is - how.

[reply]

      Well, this is not true. Names are in there, not hashed or smth. It means that you can extract them. Question is - how.

      Sure they're not. 

      $ perl -MStorable -e" Storable::nstore() "
not a reference at -e line 1.

$ perl -MStorable -e" print grep /Storable.dll/i, keys %:: "
_<C:/citrusperl/vendor/lib/auto/Storable/Storable.dll
$ grep nstore C:/citrusperl/vendor/lib/auto/Storable/Storable.dll

$ objdump -x C:/citrusperl/vendor/lib/auto/Storable/Storable.dll |grep
+ nstore

      [download]

      Where are they again?

      Like I said, you have to use a disassembler to track down "newXS" calls which "register" subs

[reply]
[d/l]

        May be they are here, in Storable.pm? 

        #
# nstore
#
# Same as store, but in network order.
#
sub nstore {
    return _store(\&net_pstore, @_, 0);
}

        [download]

[reply]
[d/l]

In Section Seekers of Perl Wisdom