Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:3622
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <2797.192.168.1.253.1059432199.squirrel@192.168.1.2>
In-Reply-To: <5.1.0.14.2.20030729011031.04d5f808@localhost>
References: <2709.192.168.1.253.1059417027.squirrel@192.168.1.2> 
     <5.1.0.14.2.20030729011031.04d5f808@localhost>
Date: Mon, 28 Jul 2003 15:43:19 -0700 (PDT)
To: zeev@zend.com
Cc: "PHP Internals List" <internals@lists.php.net>
Reply-To: mes@zeroc.com
User-Agent: SquirrelMail/1.4.0-1
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Importance: Normal
Subject: Re: [PHP-DEV] DLL export request
From: mes@zeroc.com ("Mark Spruiell")

> At 21:30 28/07/2003, Mark Spruiell wrote:
>>Hi,
>>
>>I'm prototyping a PHP5 extension creates user classes dynamically.
>>This (mostly) works, although it's apparent that PHP isn't really
>>expecting this type of activity.
>>
>>I did encounter problems when trying to build this extension on Windows,
>>however, because the following functions are not exported from the PHP
>>DLL:
>>
>>zend_do_inheritance
>>zend_initialize_class_data
>>
>>Are there any objections to exporting these functions so that they can be
>>used by extensions?
>
> Yep, they're internal and shouldn't really be used by extensions - why
> doesn't zend_register_internal_class_ex() work for you?

My extension uses these functions to create user classes, not internal
classes - it's essentially translating a specification language into user
classes dynamically. The traditional solution would have been to perform
an intermediate step of translating into PHP code first, but we prefer
this dynamic approach precisely because it avoids the administrative
issues associated with generated code.

- Mark