Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59320
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.22 cause and error)
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: "internals@lists.php.net" <internals@lists.php.net>
References: <op.wb4p5lxsidpuyk@slws007.slhq.int>
 <CAEZPtU63cgkFLEMOjAAd8kDXY8adFymPcW2f2Evi=A9r-GPzFw@mail.gmail.com>
Date: Mon, 02 Apr 2012 11:45:46 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Organization: =?utf-8?Q?N=C3=BAcleo_de_Eng=2E_Biom=C3=A9di?=
 =?utf-8?Q?ca_do_I=2ES=2ET=2E?=
Message-ID: <op.wb4tekflidpuyk@slws007.slhq.int>
In-Reply-To: <CAEZPtU63cgkFLEMOjAAd8kDXY8adFymPcW2f2Evi=A9r-GPzFw@mail.gmail.com>
User-Agent: Opera Mail/11.61 (Win32)
Subject: Re: [PHP-DEV] Addition of calendar to intl
From: glopes@nebm.ist.utl.pt ("Gustavo Lopes")

On Mon, 02 Apr 2012 11:13:02 +0200, Pierre Joye <pierre.php@gmail.com>  
wrote:

> The only thing I really dislike is the procedural API. The prefix
> "intlcal_" is not very nice, but what I really doubt is the usefulness
> of the procedural APIs for the Calendar resources. It makes little to
> no sense to have it as it brings nothing in comparison to the OO
> version.
>
> I know we could have it to be consistent with other part of the intl
> extension but ...
>

Well, it's mainly a matter of consistency. Every other part if the  
extension exposes, at least, a procedural API, and most of the time also a  
OO API. So having only an OO API would be unprecedented.

As for the usefulness, I agree it's very little, but the same could be  
said of the OO API (though the procedural API is, in fact, object oriented  
and the syntactically OO API is a better fit). Nevertheless, many people  
actually prefer to use the procedural API.

In fact, including two APIs implies some non-trivial work, because you  
have to declare the functions in two function tables, the arginfo must be  
different, you have to test both, etc. But since it's already done, the  
only issue is some extra memory and MINIT work required.

In sum, I don't think it hurts much and it helps the extension stay  
consistent.

-- 
Gustavo Lopes