Re: [PEPr] +1 for Encryption::Crypt_HMAC2

Hi Till, I noticed this cropping up as a condition - as far as I am aware lazy loading of classes, especially for rarely used Exceptions is generally okay. It does not actually break byte code caching since the opcode cache will cache the file contents (there were issues with APC esp. some time ago resolved for a long time now) - the only performance hit is that the opcode cache won't get the class/function declarations setup but the major benefit of caching the file to memory is preserved. Despite the conditions here, I'd prefer to retain the lazy loading. I see little point in loading up dozens of Exception classes in applications ;). Paddy Pádraic Brady http://blog.astrumfutura.com http://www.patternsforphp.com ----- Original Message ---- From: Till Klampaeckel <till@php.net> To: PEAR developer mailinglist <pear-dev@lists.php.net> Cc: Till Klampaeckel <till@php.net>; Pádraic Brady <padraic.brady@yahoo.com> Sent: Wednesday, July 4, 2007 5:16:06 PM Subject: [PEAR-DEV] [PEPr] +1 for Encryption::Crypt_HMAC2 Till Klampaeckel (http://pear.php.net/user/till) has voted +1 on the proposal for Encryption::Crypt_HMAC2. Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=495 Vote information: http://pear.php.net/pepr/pepr-vote-show.php?id=495&handle=till This vote is conditional. The condition is: * lazy loading breaks bytecode caching That's my only objection. I can't comment on hash vs. mhash, but I guess if the latter is deprecated (to PECL), better convert now. And I must add, that I really like your docs. -- Sent by PEPr, the automatic proposal system at http://pear.php.net -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php ____________________________________________________________________________________ Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/