[EMAIL PROTECTED] wrote:

> 
> Bill & David,
> 
> First, let me apologize for top-posting in a reply to a reply, I know it
> makes things confusing, but we use Lotus Notes and this is how it does it.

I'm sure it doesn't stop you from deleteing the unecessary text below and
I'm pretty sure your keyboard has a down arrow key which would allow you to
place your comments after the thing you're commenting on.  The only real
question is why Lotus doesn't properly quote the prior posts like every
other decent client.  My guess is it's just improper knowledge on your part
since it seems like a pretty basic thing to have in a mail client.

> The elided portion uses the same constructs for control, I just thought
> nobody'd want to wade through all 18. Also, I am comparing golden
> delicious with red delicious in the testing. That is, I'm only comparing
> the presence/absence of the /o, the rest of the code's the same (no
> interpolated vars in the elision, either).

/o shouldn't have any bearing on your code since you had no interpolated
variables in your REs.  That being said, it's possible your benchmark of
same wasn't accurate in its results (too few iterations etc).

> As regards the parens, should I not use them? I thought they were needed
> for the OR-ed possible values--was I mistaken in this?

You do need the parens in the case of your anchors on both ends.

>From your later email:

> This looked promising, but when I coded a foo-file to try it, I discovered
> that the %actions hash must be declared after the values of $row and $val
> are known--that is, inside the Translate sub itself.

That makes no sense.  If the hash is global in scope, it would be available
to the translate sub if declared prior to the sub.  Chances are, your scope
is preventing its use.

>                                                       More fiddling is
> required, but I wonder how much time would be taken by creating that
> 94-member hash 94 times as compared to evaluating the switch. Another
> problem: five of the cases elided in my original email involve executed
> code, not just grabbing a hash-member.  Any thoughts, suggestions, or advice?

The hash should be composed of anonymous subs to handle each case then.

-- 
  ,-/-  __      _  _         $Bill Luebkert    Mailto:[EMAIL PROTECTED]
 (_/   /  )    // //       DBE Collectibles    Mailto:[EMAIL PROTECTED]
  / ) /--<  o // //      Castle of Medieval Myth & Magic http://www.todbe.com/
-/-' /___/_<_</_</_    http://dbecoll.tripod.com/ (My Perl/Lakers stuff)
_______________________________________________
ActivePerl mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Reply via email to