Re: [RFC] imagettf* deprecation/removal
On Sun, Jul 27, 2014 at 7:09 PM, Lonny Kapelushnik <lonny@lonnylot.com> wrote:
>
>>> Wouldn’t it be simpler to just make them aliases?
>>
>> Indeed, and as I have no problem if Lonny likes to go ahead with this
>> RFC, I do not think we need one for such trivial change.
>
>
> Andrea,
>
> Whom are you suggesting the alias would be simpler for?
>
> Personally, I do not think it would be simpler for the userland API to have them aliased. I
> think an alias will cause unneeded confusion, discussions, and waste time in an office.
>
> Pierre,
>
> The idea behind making this an RFC is to come to an agreement on both the change and the
> timeline now so there are little/no questions later.
Yes, and I appreciate your work :)
However the idea to add yet other warnings/notices to ext/gd is not
something I like to see in GD. I will rather remove many for php-next
instead of adding more. Also some new font APIs may as well make the
whole ttf ones less relevant, see the upstream version.
I will take a deeper look at the function you refer to and see what
would fit best. If a documentation only deprecation works I will go
for it.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
Thread (16 messages)