Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

When declarative isn't really declarative More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

short circuit ops (Score:1)

by mpeters (5802)

Basically the rules are a bunch of "ands" or short circuit operators right? So the order doesn't matter for anything but execution speed. So if you have

common_but_lengthy() && rare_but_short()

It should be re-written as

rare_but_short() && common_but_lengthy()

Not because it's any more correct, but because as you point out it saves time. So switching the order of how F::F::R does things shouldn't affect the correctness right?
- Re:short circuit ops (Score:1)
  
  by Alias (5735) on 2008.05.14 21:47 (#62859) Homepage Journal
  
  There are some subtleties involved for pruning, purging, boolean combinations etc.
  
  But I _THINK_ that if you have a simple state rule, immediately followed by a simple name rule, that case can always be swapped.
  
  Reply to This
  
  Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.