Re: Proposal for a new extension AMFEXT

Hi, I agree totally with you. At the time of the API design for AMFEXT with Patrick we thought of having a simple function based approach to keep it simple. Instead the StringBuilder is just an experiment and for me the resource approach was just working, I can make it an OO class. Best, Emanuele > On 6/6/07, Stanislav Malyshev <stas@zend.com> wrote: >> Hi! >> >> > can you give me some details about your suggestions? >> >> Sure. One can wrap arbitrary data in object as well as in resource, and >> the use it both regular API and procedural API - like mysqli does or >> ext/unicode/collator.c in php HEAD (the latter is easier to >> understand :) >> >> Object representation might be better since one could, for example, >> inherit class or easily define operations like converting to string. > > I would suggest to simply deprecate the procedural API and use only > object. It is easier, flexible and users prefer to use OO API these > days. That's what I do in Zip. The procedural API will not get any > improvement or new features. New devs are done only for the OO api. > > --Pierre -- Emanuele Ruffaldi Research Fellow - PhD. Scuola Superiore Sant'Anna di Pisa PERCRO Lab - Virtual Reality and Telerobotic Systems Division via Martiri 11 56100 Pisa - ITALY Tel.: +39 050 838 980 Fax.: +39 050 883 333 E-mail: emanuele.ruffaldi@sssup.it Web: http://www.teslacore.it

Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc