Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85865
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.171 as permitted sender)
Message-ID: <5532C978.7030009@gmail.com>
Date: Sat, 18 Apr 2015 14:15:36 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: georges <geolim4@gmail.com>, PHP Internals <internals@lists.php.net>
References: <CACjyb+wzguSRSW5qz-bLT1GU4xbQjFk-4VyaQjMasQ+e1xDn=w@mail.gmail.com>
In-Reply-To: <CACjyb+wzguSRSW5qz-bLT1GU4xbQjFk-4VyaQjMasQ+e1xDn=w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] RFC: spl_autoload_register() should provide kind of
 entity to load
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> Currently spl_autoload_register() pass the name of the class entity to the
> first *Callable* argument​, but there is now way (as i far i know) to know
> what kind of entity we're looking for.
> -Class ?
> -Interface ?
> -Trait?

I'm not sure it would be very useful for the engine. It is obviously
useful for your particular naming scheme, but most people do not use
this scheme, so this is not very common use case. I'd even argue it
usually not the best practice, as class and interface names may be used
interchangeably in typed parameters, return types, instanceof checks,
etc. and one could convert class to interface easily without breaking
anything (except your naming scheme).

Also, while in the many common cases it is known which entity is
required, there's no guarantee it is known in all cases and I'm pretty
sure there could be cases where it's not known - in fact,
zend_lookup_class() API has only the name as its input.

-- 
Stas Malyshev
smalyshev@gmail.com