Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I'm currently working on a script to performs auto-categorisation of data elements based on rules generated from their characteristics.

These categorisation rules change periodically, and hence I've created a rules file to perform the categorisation and return a suitable category and reason to the calling sub.

My problem: I'm struggling to have eval return anything. According to the docs:

In both forms, the value returned is the value of the last expression evaluated inside the mini-program; a return statement may be also used, just as with subroutines.

.. but that doesn't seem to work for me.

A typical rule might look like the following, where $abs_diff and $source are defined within the sub performing the eval:

return( "A", "Cat A" ) if $abs_diff < 75_000 and $source eq "ICE";

I've tried the following:

# process analysis rules foreach( @$analysis_rules ) { eval $_; }
and
# process analysis rules foreach( @$analysis_rules ) { my( $cat, $comment ) = eval $_; return( $cat, $comment ) if $cat and $comment; }
among a bunch of variations without luck.

Can anyone see where I'm going wrong?

Thanks in advance ...

Update: Fixed a typo in the rule - thanks to holli for pointing that out :)

In reply to Returning data from an eval by Tanalis

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (4)
As of 2024-04-18 19:00 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found