Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65483 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54892 invoked from network); 30 Jan 2013 10:23:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Jan 2013 10:23:33 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain zend.com does not designate 209.85.219.42 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.219.42 mail-oa0-f42.google.com Received: from [209.85.219.42] ([209.85.219.42:42391] helo=mail-oa0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B0/68-09318-4A4F8015 for ; Wed, 30 Jan 2013 05:23:33 -0500 Received: by mail-oa0-f42.google.com with SMTP id i18so1190591oag.15 for ; Wed, 30 Jan 2013 02:23:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:references:in-reply-to:mime-version:x-mailer :thread-index:date:message-id:subject:to:cc:content-type :x-gm-message-state; bh=lPbO+X9wgiMuHm7IxvwOH72SGP7jnrMW+aDNemtimiM=; b=A8HqxV1bzMaa3t0sZvoBjzKYkrkoYaKtwgkwCJQfL13KwJEg1qYtPosU3WWbGQ1xNA DZwSI+P3Co4r/5hXlhgBzhILMhGoUooVyWnUr4iJRF2wgykeJAGZiCnH4Nqqzj4yyNDc dtlHbk6sGTpDk5xOEpkEbF2nemmwKBGuGJc/RlFoqFXpsPKoQGXewuOoElGq7TfT24SK 9haVcJKx3NrgS6sm9yYpUvEBwDLmdS06R4kP44tTMb3PyQ8dOykf1Nvf2tf4K4b5w3nY TcIadxUb0062lJK4lBzJMaliHuQRwwB8DTPls96Q/O5fat8v7rGL5ivR8SLzj7Jn66Yf kYKQ== X-Received: by 10.60.32.19 with SMTP id e19mr3311446oei.60.1359541409209; Wed, 30 Jan 2013 02:23:29 -0800 (PST) References: <5d21b42656d49b4a71d9f808541bd745@mail.gmail.com> <51078485.30107@rotorised.com> <11e1ccc6eca996d9d94ae9a3bff0bbab@mail.gmail.com> <5108667C.1030901@oracle.com> <510868DE.7010408@lerdorf.com> <5108749D.8090608@oracle.com> In-Reply-To: <5108749D.8090608@oracle.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIqL8waXVttbugrqkVxisGQEOzMkQHRgNAlAWVktVQB8hlHcAKgcleRAjdBEz+XWT538A== Date: Wed, 30 Jan 2013 12:23:28 +0200 Message-ID: <755cf1481dd9db952bb757c2f246168b@mail.gmail.com> To: Christopher Jones Cc: internals@lists.php.net Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkjp/Rvwp///hnYDKiUTYKiAhmB0lLtVXIVXrQlsAinM87faCz9WGZjBF8RHUaLKbSi49smXH6a2p7xkWuS9Qk5qys3uW+XEHlU5g+g3aoiQxA5VNxOb2F+rOmASzM9/ynPC4B0 Subject: RE: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP distribution From: zeev@zend.com (Zeev Suraski) > > XDebug together with an opcode cache is always a shaky thing and not > > something we should be too concerned about. You would never want to > > run both in production. It would be good if they didn't clobber each > > other for dev environment purposes, but I am sure we can figure that > > out. > > This is the kind of info the RFC (and then user doc) should have. It should be easy to implement the same behavior we have with Zend Debugger today also with Xdebug. The debugger essentially intercepts the compile() callback before Optimizer+, and if it determines that the present request should run through the debugger - it bypasses the Optimizer+ altogether and calls directly into zend_compile_file(). I'll update the RFC that it should be possible to integrate it nicely with any other modules. Zeev