Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3806298
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 19, 20262026-05-19T14:48:49+00:00 2026-05-19T14:48:49+00:00

I found a possible bug in perl’s closures and $1 regexp variables. Simply, they

  • 0

I found a possible bug in perl’s closures and $1 regexp variables. Simply, they don’t mix together.

Let’s take this code.

use warnings;

while ("1234567890"=~/(.)/sg) {
    push @subs, sub{print $1;};
}

for (@subs) {$_->()}

You would imagine that perl will now print all the numbers – instead, I got 10 warnings from undefined $1.

Is it really a bug, or did I just missed something in perl documentation? Is there some reason, why should $1 be undefined and NOT being part of the closure?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-19T14:48:50+00:00Added an answer on May 19, 2026 at 2:48 pm

    I think the answer is similar to the answer to perl closures and $_. $1 is a global variable, too.

    What you need to do is:

    my $x = $1;
    push @subs, sub{print $x;};
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I've found a possible bug while i was using jquery and Ajax function on
I just found a possible bug in Firefox 6 for Windows. When I try
I have found possible slowdown in my app so I would have two questions:
I found a topic on MSDN that talks that yes, this is possible. I
I have looked on FaceBook Developer page and found that it's possible to create
Found this rather strange bug in IE8; element.style.top is limited to 1342177 pixels. Even
We've found a bug in a program that we bought from another company, which
If you find a bug in a package, it's usually possible to patch the
Possible Duplicate: Floating point inaccuracy examples PHP rounding issue - Is this a bug?
I've found small bug in tinymce styleselect. I've submitted bugreport already (http://tinymce.moxiecode.com/develop/bugtracker_view.php?id=4576) but I

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.