Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Fri, 14 Mar 2003 09:05:07 -0500
To: Andi Gutmans <andi@zend.com>
Cc: PHP Internals <internals@lists.php.net>
Message-ID: <20030314140506.GH24185@hyperion.gravitonic.com>
Mail-Followup-To: Andrei Zmievski <andrei@gravitonic.com>,
	Andi Gutmans <andi@zend.com>,
	PHP Internals <internals@lists.php.net>
References: <20030313205122.GA21734@hyperion.gravitonic.com> <5.1.0.14.2.20030314142807.0e2af870@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.1.0.14.2.20030314142807.0e2af870@127.0.0.1>
User-Agent: Mutt/1.4i
Subject: Re: [PHP-DEV] Doc comment patch
From: andrei@gravitonic.com (Andrei Zmievski)

On Fri, 14 Mar 2003, Andi Gutmans wrote:
> Hmm. I thought introspection is reflection. It seems I misunderstood.

I think that introspection is a superset of reflection.
> Are you sure it's worth bloating the engine to hold this extra information?

It is possible that an extension or a PEAR class could parse through the
file and extract the doc comments, but since the engine is already doing
the scanning/parsing, I thought it might be very convenient to use it.
Yes, the structure will need to have extra fields, but how much bloat
are we talking about? And if the reflection is to be good, it _will_
need additional information from the engine, such as the function
parameter names, class type hints, etc - all this needs to be stored
somewhere and it can't be an extension since it can't hook into the
scanning/compilation process.

If you don't like this approach, I am open to ideas.

-Andrei                                       http://www.gravitonic.com/

"The time from now until the completion
 of the project tends to become constant." -- Douglas Hartree