Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25629
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain broadpark.no from 80.202.4.58 cause and error)
Date: Tue, 12 Sep 2006 07:12:29 +0200
To: Stanislav Malyshev <stas@zend.com>
Cc: internals@lists.php.net
Message-ID: <00c601c6d62a$0be44e80$9a02a8c0@pc>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7BIT
References: <015801c6d4d5$6440d1d0$9a02a8c0@pc>
 <7f3ed2c30609100744x7a5d4fdfs9601ae4671b351d3@mail.gmail.com>
 <003401c6d4ee$1b251d80$9a02a8c0@pc>
 <1803358544.20060910173549@marcus-boerger.de>
 <29.48.46429.82A54054@pb1.pair.com>
 <10845a340609110106y5a21de3coc98659cde5ef0465@mail.gmail.com>
 <450591E5.7080402@zend.com> <004e01c6d5c9$5f9b16a0$9a02a8c0@pc>
 <4505A549.4040004@zend.com> <002401c6d5d1$7c180d30$9a02a8c0@pc>
 <4505CA2C.7080100@zend.com>
Subject: Re: [PHP-DEV] Re: __autoloading and functions
From: tslettebo@broadpark.no (=?UTF-8?Q?Terje_Sletteb=C3=B8?=)

> > In either of the above cases, you specify where a function belongs, both
> > where it's defined, and where it's used (either through full
qualification,
> > or a shorter one, using "import"). I'm not arguing for a function to
> > "magically" become a part of a class/module/whatever, if you thought so
> >
> Then the question is how do you think this function would be used?

That's a very good question... One "simple" answer would be to have one file
per function, and have it work like typical class autoloaders. However, that
could be too much overhead (on many levels), having a lot of small files,
that conceptually belong together.

Maybe function autoloading isn't such an obvious feature, after all (which
was one reason for bringing it up - getting the pros and cons of it. By the
way, I've now also read in on the archive of this and the other issues
having been mentioned in this thread, such as namespaces).

Regards,

Terje