Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
rather first figuring out what other overloads will be really
needed. At the moment I can't see anything useful, but '==', '""' and
'0+'.
String comparisons shouldn't be even offered, IMHO. Users should check
the error code
No good, IMO. How users trap errors is for them to decide, not us.
Their eval blocks might be wrapping a large section of third-party
code, and not all of the trapped exceptions will come from mod_perl.
that's why they first need to check
if (ref $@ eq 'APR::Error') { check rc code here }
but what do I know, all I see is the tests...
If it were my decision, I'd set fallback => 1 and optimize that by
providing subs for the common operations, like '=='.
sounds good to me. Go for it then, Joe.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
