Skip to content

modernize the documentation about $& and similar variables#24286

Open
damil wants to merge 1 commit intoPerl:bleadfrom
damil:update_regexp_doc
Open

modernize the documentation about $& and similar variables#24286
damil wants to merge 1 commit intoPerl:bleadfrom
damil:update_regexp_doc

Conversation

@damil
Copy link
Copy Markdown

@damil damil commented Mar 15, 2026

current documentation about variables $&, etc. still mentions performance penalties ... this is no longer true since Perl 5.20.0

  • This set of changes does not require a perldelta entry.

…t these variables incur performance penalties
@Grinnz
Copy link
Copy Markdown
Contributor

Grinnz commented Mar 15, 2026

perlfaq is maintained on CPAN and so changes to it must be contributed upstream at https://github.com/perl-doc-cats/perlfaq.

@Grinnz
Copy link
Copy Markdown
Contributor

Grinnz commented Mar 15, 2026

I'm not certain the $& / /p issue has been completely ameliorated, as has been recently discussed on p5p. Unfortunately the NNTP archives currently seem to be not responding so I cannot link the discussion.

@jkeenan
Copy link
Copy Markdown
Contributor

jkeenan commented Mar 23, 2026

I'm not certain the $& / /p issue has been completely ameliorated, as has been recently discussed on p5p. Unfortunately the NNTP archives currently seem to be not responding so I cannot link the discussion.

@Grinnz how do you think we should handle this patch? It changes two files, one of which needs to be sent upstream first, while the other is in P5P jurisdiction? Can one be changed without the other (in either direction)?

@Grinnz
Copy link
Copy Markdown
Contributor

Grinnz commented Mar 24, 2026

The changes can be considered separately. The change to the core perldoc should be evaluated on its accuracy by someone with more knowledge of these details than me.

@Grinnz
Copy link
Copy Markdown
Contributor

Grinnz commented Mar 24, 2026

Here is the most recent discussion on /p on the list: https://www.nntp.perl.org/group/perl.perl5.porters/2026/02/msg270725.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants