Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:8669
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Organization: Emini I/S
To: Georg Richter <georg@php.net>
Date: Tue, 23 Mar 2004 12:52:55 +0100
User-Agent: KMail/1.6
Cc: internals@lists.php.net, Marcus Boerger <helly@php.net>,
	john@coggeshall.org
References: <1079935882.5524.0.camel@coogle.localdomain> <200403222327.08315.edink@emini.dk> <200403231158.06420.georg@php.net>
In-Reply-To: <200403231158.06420.georg@php.net>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-ID: <200403231252.56196.edink@emini.dk>
Subject: Re: [PHP-DEV] Studlycaps and MySQLi
From: edink@emini.dk (Edin Kadribasic)

On Tuesday 23 March 2004 11:58, Georg Richter wrote:
> > I agree with Marcus (and I think Andi) here. If its not too much trouble
> > OO interface to mysqli should IMHO follow the same conventions other OO
> > extensions do,
>
> beside changing c-code it's
> - changing documentation (english, german, spain and french)
> - changing all samples
> - changing testcases (incl. ~300 testscripts on my machine)
> - changing ~200 slides
> - changing 2 articles
>
> and 2 authors told me they don't have a chance to change it anymore in
> their books, they will be printed these days.
>
> you think it's not too much trouble?

Since we're at "now-or-never" point I guess the trouble would be worth it. I 
know its a lot of work but it should mostly be search & replace type. 

The book authors are probably already aware of the risk of writing about 
pre-release version of opensource software.

Edin