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

  • Home
  • SEARCH
  • 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 6206995
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T05:32:56+00:00 2026-05-24T05:32:56+00:00

eval{ require $file; } /*subsequent code goes here*/ … If $file contains an exit

  • 0
eval{
   require $file;
}

/*subsequent code goes here*/
...

If $file contains an exit statement, the subsequent code doesn’t have a chance to run.

How to work around so that the subsequent code always get its chance to run when eval is done??

  • 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-24T05:32:58+00:00Added an answer on May 24, 2026 at 5:32 am

    It’s not possible to abort the exit call. $file should use die instead, which can be trapped by an eval.

    As a workaround, you can override the exit builtin globally:

    BEGIN {
        *CORE::GLOBAL::exit = sub { die "About to exit" } 
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have some lisp initialisation code: (eval-when (:compile-toplevel :load-toplevel :execute) (require 'asdf)) (eval-when (:compile-toplevel
I have a eval function like this if(FALSE === @eval($code)) echo 'your code has
In schedule.rb file, the statement: require #{RAILS_ROOT}/config/environment.rb every 10 10 2 * * *
I have a .js file with code compatible for both php and js languages.
The eval function is a powerful and easy way to dynamically generate code, so
I can do an eval(something()); to execute the code dynamically in JavaScript. Is there
procedure MyProc(Eval: Boolean); begin if not Eval then Exit; /* do stuff */ /*
I have some javascript: eval('var incomingJSON =' + ajaxObj.responseText); for (p in incomingJSON.common) {
I have seen bind and eval used interchangeably especially in ASP.NET GridViews. What is
I have a Moose class that i would like to store using Apache::Session::File. However,

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.