Well, it depends on what the issue is. For things where the php5 language change broke compatibility (e.g. object
copying where the language changed), Quercus is php5, and we won't make any changes to > try to resolve it. In that case, you're exactly right.
There may be some issues where Zend's implementation of php5 broke
compatibility (e.g. introducing bugs) in a way where we can work with both. I can't recall any
case like that, but it's possible. so i still think in this case getting the codebase running under a
mod-php5 system first,
then attempting a port to quercus is the way to go.
-nathan On 6/14/07, Scott Ferguson <[EMAIL PROTECTED]> wrote:
On Jun 14, 2007, at 9:43 AM, Nathan Nobbe wrote: > Ok. There's a decent chance it's a Quercus bug, then. if the app doesnt run under mod-php5, how can you blame quercus? i mean what is the stance of quercus, is it supposed to emulate mod-php4 and mod-php5 or just mod-php5? Well, it depends on what the issue is. For things where the php5 language change broke compatibility (e.g. object copying where the language changed), Quercus is php5, and we won't make any changes to try to resolve it. In that case, you're exactly right. There may be some issues where Zend's implementation of php5 broke compatibility (e.g. introducing bugs) in a way where we can work with both. I can't recall any case like that, but it's possible. -- Scott -nathan On 6/14/07, Scott Ferguson <[EMAIL PROTECTED]> wrote: > > > On Jun 14, 2007, at 8:59 AM, [EMAIL PROTECTED] wrote: > > > Thanks for your response. I'm not familiar with PHP, so at this > > point unfortunately I cannot give you a specific technical example > > of an error - at least not one that would help you diagnose the > > problem. My description would be too high-level, such as "when I > > press this button, it doesn't work." > > > > On the other hand, I look at your list of rather complex applications > > that run under Quercus without problems (phpMyAdmin, phpBB, etc.) and > > think that this application should be able to work properly under > > Quercus. Again, how can I determine this without knowing much PHP. > > Ok. There's a decent chance it's a Quercus bug, then. > > Our main development goals for Quercus for the rest of the year are > working towards getting 100 PHP applications running on Quercus and > closing bugs as they're reported. > > Because PHP isn't a specification-based language, and because the > libraries are extensive and sometimes strange, the only way to really > ensure that Quercus is correct is to get lots of existing > applications running correctly. > > We're still at the stage where many/most new applications we try > uncovers some library bug or language quirk that Quercus doesn't have > working exactly like PHP. > > -- Scott > > > > > If I am able to produce a very specific bug in the application and > > narrow down the source php file that causes the error, I'll post it > > here and hopefully you can determine if it's a Quercus bug or not. > > > > If you have any suggestions, please let me know. > > Thanks very much for your help. > > > > Fred > > -- > > > > [EMAIL PROTECTED] > > > > > > > > _______________________________________________ > > resin-interest mailing list > > resin-interest@caucho.com > > http://maillist.caucho.com/mailman/listinfo/resin-interest > > > > _______________________________________________ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest > _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
_______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
