Re: cvs: php4 /ext/saprfc CREDITS EXPERIMENTAL Makefile.in README config.m4 php_saprfc.c php_saprfc.h /ext/saprfc/tests 001.phpt

Andrei Zmievski wrote: > > On Tue, 01 May 2001, Sterling Hughes wrote: > > Why not wait until you have a basic functionality set before adding it to > > PHP? > > Good point. Nothing prevents you from developing locally, Hartmut, and > then submitting to CVS. > > -Andrei one practical reason: i want to continue this at work today and getting through our firewall from dial-in account is rather difficult (and i had no floppy at hand) and a lot of philosophical ones: - the first thing i learned about CVS was "commit often, commit early" - i'd like to have release history for this even in this early state (and there is no such thing as a distributed repository in CVS) - others might be interested in this as well and might even know more about what i'm doing here. the earlier peer review sees something done wrong or suboptimal the better - it doesn't hurt. if it does then i have done something wrong in implementation i would want to know about asap (peer review again) - someone else might by chance even work on the same thing if both of us would work in private until we had it all working we would not only duplicate the effort for this but would also have to spend additional time to merge our solutions or to decide for one of them to stay and the other to go away (not very likely in this special case, but a general issue) and finally a psychological one: - by making this public i put myself under pressure to finish it -- Hartmut Holzgraefe hartmut@six.de http://www.six.de +49-711-99091-77