On Apr 8, 2005, at 9:54 PM, George Schlossnagle wrote:
It would be pretty different. Some of the major differences are:
1) Use of it's own SAPI for tighter integration rather than using the
rather hobbled embed SAPI
2) The ability to access back into the perl interpreter to directly
call perl methods and access perl variables
3) Using the php5 object overloading capabilities to affect the Perl
environment from within PHP
4) Support for instantiation of multiple concurrent PHP intrepreters
As far as converting the existing PHP module, I guess anything is
possible, but it would require a major rewrite and I'd rather focus on
making this work the right way instead of convincing someone else to
let me merge work into their project.
I guess I'm not convinced, since #2,3,4 would just be additions to
PHP.pm's functionality, and #1 is just a change in its implementation.
It would seem that it can all be done in a backward-compatible way.
If you had said "PHP.pm is for doing X, but this module is for doing
Y", then I'd think you'd have a case for starting a new module. But
you're just adding to X.
In any case, you can certainly work out all the things you need to work
out in your own namespace first, then worry about merging into PHP.pm
later.
-Ken
|
