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. Does anyone agree? Is there interest in doing this? -- Kee Hinckley - Somewhere.Com, LLC http://consulting.somewhere.com/ [EMAIL PROTECTED] I'm not sure which upsets me more: that people are so unwilling to accept responsibility for their own actions, or that they are so eager to regulate everyone else's. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
