Re: TSRM compatibility note

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi zeev, is there a short explanation of this tsrm stuff somewhere ? i'd like to know which kind of functions should take use of the tsrm features. while reviewing your changes to the ext/com module i'm stumbled into a few inconsistencies (as far as i can follow). where on one hand you exaggerated in adding TSRM_* macros you left out very important functions on the other hand. maybe i'm wrong and i misunderstood the function of these macros, so a short HOWTO would be essentially. - -harald. "Zeev Suraski" <zeev@zend.com> schrieb im Newsbeitrag news:<5.1.0.14.2.20010730101740.050bb618@localhost>... > Just FYI - code working with the old-style TSRM should still go on > working. It just wouldn't take advantage of the faster single fetch > approach we switched to. > > We should probably change ext_skel to generate new-style fetches and > macros, so that new extensions take advantage of the faster approach. > > Zeev > -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBO2Wt5a1+myS9SSHxEQK2rACfYQ9FrNoszFW4pHL1y/iE3bRb1HUAn1Jy W4GO6+3JUAeUgYNFsb7LB8y+ =PdxQ -----END PGP SIGNATURE-----