Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:61992 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24047 invoked from network); 3 Aug 2012 07:08:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Aug 2012 07:08:43 -0000 Authentication-Results: pb1.pair.com header.from=leight@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=leight@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender) X-PHP-List-Original-Sender: leight@gmail.com X-Host-Fingerprint: 209.85.216.170 mail-qc0-f170.google.com Received: from [209.85.216.170] ([209.85.216.170:55443] helo=mail-qc0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E6/52-09659-AF87B105 for ; Fri, 03 Aug 2012 03:08:43 -0400 Received: by qcmt36 with SMTP id t36so230244qcm.29 for ; Fri, 03 Aug 2012 00:08:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=+4/YxlFPD1uOlNqb9TnxfhysQMheofqzhypdYdvetHQ=; b=Tqdzd4QTJqB/slu3ubd+Pr39apm4TfhwjeG6In4JPLVq29fyv2Zkrg49tjPtj9zJcI Jc5IAhoGNe9NQCWWugNx1SbXq9s47LEbd4cXD0KCYAsNZ/GrjQ4fiAVZRD4LzRQ0q2/S YpUv9nF/HjF7ltLbnao2gUW/L3cTXUrnXXSXug1cS60e0kzOhZPNmNkk+DHeVeGXxvyr MWlC51b4bQH6WVVh8dzkw7yWr/eHOZuLrcSaFJ7/KAb9CvdlonvEJDjLB/zOUBew2t1U eNHdZZbSubgd4U6YY8M2tpBiPzNgAovy2eJ/NZoMRUnUkXeEiH2HYvYvUkXfIlyoSUwc CMwA== MIME-Version: 1.0 Received: by 10.229.135.206 with SMTP id o14mr305852qct.91.1343977720172; Fri, 03 Aug 2012 00:08:40 -0700 (PDT) Received: by 10.229.149.203 with HTTP; Fri, 3 Aug 2012 00:08:40 -0700 (PDT) Date: Fri, 3 Aug 2012 08:08:40 +0100 Message-ID: To: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Subject: Why do disabled functions / classes generate a WARNING. From: leight@gmail.com (Leigh) Hi all, Can anyone explain to me the reason that when a function or class is disabled via the ini setting, an attempt to access the disabled item generates a non-fatal error? I'm looking at a segfault in the SPL caused by the blind creation of a class, which seems to only fail when the class is disabled. I'm wondering in how many other places this could occur. The obvious solution is to be more careful and check return values, but a FATAL would also have prevented execution continuing. Thanks, Leigh.