develooper Front page | perl.perl5.porters | Postings from August 2019

Re: Help identify core-only functions marked as experimental

Thread Previous | Thread Next
From:
Paul "LeoNerd" Evans
Date:
August 14, 2019 12:00
Subject:
Re: Help identify core-only functions marked as experimental
Message ID:
20190814125952.169330db@shy.leonerd.org.uk
On Wed, 31 Jul 2019 16:46:45 -0600
Karl Williamson <public@khwilliamson.com> wrote:

> I am now in the process of making this new flag.  I have found many 
> functions that I'm confident were marked experimental only for the 
> purposes I mentioned above, but there are another 150 that I'm unsure 
> of.  Please examine the list below and let me know your take on them. 
> You can use #irc to avoid the email overhead if you wish.

Of your original list, according to `nm -D` on Future/AsyncAwait.so,
here's what I am using:

                 U Perl_lex_bufutf8
                 U Perl_lex_peek_unichar
                 U Perl_lex_read_space
                 U Perl_lex_read_to
                 U Perl_lex_read_unichar

                 U Perl_parse_block
                 U Perl_parse_fullexpr
                 U Perl_parse_termexpr

                 U Perl_sv_free2

(some subset of these are also used by some of my other syntax modules)

Also the various #defines:

                   PadARRAY
                   PadMAX
                   PadlistARRAY
                   PadlistNAMES
                   PadnameLEN 
                   PadnameOUTER [wasn't on your original list but maybe should be?]
                   PadnamePV
                   PadnamelistARRAY
                   PadnamelistMAX

Also various variables:

                   PL_comppad
                   PL_curpad
                   PL_keyword_plugin

Also various static functions:

                   cx_pushblock
                   cx_pusheval

Additionally I would like

px	|LOGOP*	|alloc_LOGOP	|I32 type|NULLOK OP *first|NULLOK OP *other

but it isn't available on non-ELF so I had to copypaste a simpler
version of it.

> I think that after this is done, anything that is still marked as 
> experimental and part of the API should go in perlapi.  This would
> catch the new parse_subsignature() function properly, as I believe
> it's designed for XS writers, but has to be marked as experimental.

Ah that'll be my fault, I was cargo-culting the prevailing structure of
the other ones.

-- 
Paul "LeoNerd" Evans

leonerd@leonerd.org.uk      |  https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/  |  https://www.tindie.com/stores/leonerd/

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About