Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23068
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <44567B27.5030808@mysql.com>
Date: Mon, 01 May 2006 23:18:31 +0200
Organization: MySQL AB
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050219
MIME-Version: 1.0
To: Brandon Fosdick <bfoz@bfoz.net>
CC: internals@lists.php.net
References: <4454491A.3090303@bfoz.net>
In-Reply-To: <4454491A.3090303@bfoz.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] resources vs objects?
From: andrey@mysql.com (Andrey Hristov)

   Hi,
Brandon Fosdick wrote:
>> From the point of view of an extension, what's the difference between 
>> a resource and an object? Is there any reason to favor one over the 
>> other?
> 
> 
> sqlite seems to use resources for the procedural interface and objects 
> otherwise. Whereas mysqli uses objects all around in user space, but 
> then maps them to resources in the background. Why use objects only to 
> map them to resources? Are resources somehow special?
> 

mysqli does not use resources at all. Even in the procedural interface,
the "resources" are just objects. Thus, procedural and OO code can be
mixed, for those wanting to write spaghetti code or for legacy and
non-legacy code.

$c = mysqli_connect(....);
$r= $c->query();
...


Cheers,
Andrey