Hi,
Maybe this topic occured already, then sorry when I'm wasting your time,
but I'm wondering, why there is no autoloading for functions and
(namespace)constants.
When a class is not found, then an userland function is called. Thus I
don't see a reason, why something like this doesn't
Hi:
maybe Yaf_Loader can be used for meet this requirement.
it's a internal autoload function:
Each namespace separator is converted to a DIRECTORY_SEPARATOR when
loading from the file system.
Each _ character in the CLASS NAME is converted to a
DIRECTORY_SEPARATOR. The _ character
There is lazy loading for functions via apc.lazy_functions (although I've
not properly tested this yet). That doesn't require any userspace code
changes.
For define() I'm not aware of anything allowing for lazy loading constants
(define() is just a function call).
However there are a few
Hi,
thanks for your reply, but I'm not talking about class loading (because
thats already possible). I'm talking about autoloading of userspace
functions and constants
// /path/to/my/functions.php
namespace my\functions;
const THING = 'I am constant!';
function helloWorld () {
echo
Hi,
Thanks for your reply
Am 26.07.2011 10:35, schrieb Nathaniel Catchpole:
There is lazy loading for functions via apc.lazy_functions (although I've
not properly tested this yet). That doesn't require any userspace code
changes.
As far as I can see this is for built-in functions only. The
On Tue, Jul 26, 2011 at 10:39 AM, Sebastian Krebs
sebastian.krebs.ber...@googlemail.com wrote:
Hi,
thanks for your reply, but I'm not talking about class loading (because
thats already possible). I'm talking about autoloading of userspace
functions and constants
//
As far as I can see this is for built-in functions only. The problem I see
is, that APC cannot know, where my functions are located and therefore
cannot load it without userspace help.
No it includes userspace functions. My knowledge of APC internals is very
weak, but more or less when
Hi,
Thanks, that looks similar to what I'm looking for. It doesn't seem,
that any of the reply is really against autoloading of functions (and
maybe constants), but are against the given implementations (because
they are built on top of the outdated __autoload() function), what
brings me
