On Wed, 13 Mar 2002, Kee Hinckley wrote: > It sometimes scares me how popular PHP has become. Aside from not > being thrilled with it in general (bastardized Perl with a weak > architecture), I also don't want to be stuck using a templating > solution that gets marginalized. (Been down that path before, for > years I used a embedded Perl solution I wrote in 1995. It's still > out there on at least one site.) > > What I was wondering was whether it might make sense to provide a > good set of migration tools so that PHP users could move to Embperl. > The new recipe system provides some of the necessary syntactic sugar. > But most important is providing all the calls that PHP provides. > Basically you want a Perl library that Embperl can load which > provides a compatible API. > > It seems to me that with a group effort, this wouldn't be terribly > hard, and would provide some useful routines for the Embperl (and > other Perl-based) community.
Another possibility would be a swag at a PHP to Embperl converter. I believe this would be a bit more ambitious than my csh to ksh converter I'd written in 1996 to cope with a group at work that insisted on using csh because 'it is a standard shell shipped with the OS'. Nevermind that ksh is also standard for those OSes that ship csh still, and actually works for what they were wanting to do... This would still require the library, but I don't have any problems with that; I merely mind the syntactic sugar. It probably wouldn't require as big of a library, because some of the functions already have identical functionality with a different name. However, I'll point out that this wouldn't be quite as easy as you may be thinking, as PHP has different scoping rules than perl - in PHP, everything's local (my) unless/until it's declared global. Nothing is local (local), last I checked. Ed --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
