Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96122 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71447 invoked from network); 23 Sep 2016 21:58:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Sep 2016 21:58:22 -0000 Authentication-Results: pb1.pair.com smtp.mail=danack@basereality.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=danack@basereality.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.217.171 cause and error) X-PHP-List-Original-Sender: danack@basereality.com X-Host-Fingerprint: 209.85.217.171 mail-ua0-f171.google.com Received: from [209.85.217.171] ([209.85.217.171:36080] helo=mail-ua0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 92/E3-51000-E75A5E75 for ; Fri, 23 Sep 2016 17:58:22 -0400 Received: by mail-ua0-f171.google.com with SMTP id 15so58824827uai.3 for ; Fri, 23 Sep 2016 14:58:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DKW2ZdD5+BVLOW+y37vZsf+W0p5YZAX0zZ+qfu1KKTM=; b=pyJlzu3oe7TsMoDbCGYiEEvN2ZonHvX7aGt6Zx8/LMWIIAGxMLPI4b5BKn7/MlRpgF czg9w5P75HabyG4jkSrsmiH2pVBmsassVduSI/nEyzKj8k2zIbGCABQ4EZfCc+85JiPi olJpqoXrL/4+9xeDmkFdVd/0hZ37fmuVaJhDpbb2P/4kPU4R2xvUyDn9wWAQLW7aX8B3 1hGMDtfD6kWXcWMz+CAk4LYyKPLcywa0gzIL+rza9C9hMIxuveC5okL8oYmGoOk1E9fB VaRPnUeNuakd1ToDVKAL0mICiWl7guvqs1K4D1pDESql+ant0S9F7eUMQdgtIuOBr/Gj 5Blg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DKW2ZdD5+BVLOW+y37vZsf+W0p5YZAX0zZ+qfu1KKTM=; b=OvqbRSVGadjGUyy2PABSnq5xMe4AwPpWDWlPSC6jBNNcstku5/jlUYqgyAgCSJvhYp NHy+awhPXWMOO7n1mzOJRJCOaEz7iY1jY4SLG0B6g0BuwPVTOHzS+crDYg+3OWFviguY jHhsLeFhF2Gcqod/Pcg4dl8LLVu871qvxcorjswULFCqTXzlbU0k3mHC5wNe8KYitf7i rVx27mLqFuY6cAx0Hx50ib+hpZ4l819fMLH9I/7449uggWaLhIRuboDQotX9n7QzMCL7 YCwfZPVYI/VDTfXB1ylsNN0YAq8feeQ/MAngvxIAY8wRcv6E0vVcrZkzdQtXjvibfTuf jZOQ== X-Gm-Message-State: AE9vXwNeVeWq3ZLPENXTx70ig33ER2+4xkK3ix38s2zpgxWYGyq62ML3quNZr3b2Zdy48s+v6c4wpVmvMcbjLw== X-Received: by 10.176.4.86 with SMTP id 80mr6226572uav.1.1474667900125; Fri, 23 Sep 2016 14:58:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.69.4 with HTTP; Fri, 23 Sep 2016 14:58:19 -0700 (PDT) X-Originating-IP: [2.99.239.160] In-Reply-To: References: Date: Fri, 23 Sep 2016 22:58:19 +0100 Message-ID: To: Stanislav Malyshev Cc: Nikita Popov , PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] Namespace-scoped declares From: danack@basereality.com (Dan Ackroyd) On 23 September 2016 at 20:45, Stanislav Malyshev wrote: > Imagine how > fun it is if somebody's action in different code module wouldn't just > mess up some data - it would actually break your code by changing > language semantics for your code! If you are concerned about libraries modifying how code is run, the same theoretical problem exists with libraries that register autoloaders - 'omg they can totally change what code is even going to be run, let alone the precise semantic behaviour'. This turns out not to be a problem, as any library that did that would lose all of it's users immediately. For this RFC, it would be usual to only have the namespace_declare() in the same place as the autoloader(s) are registered; in the bootstrap file before any real code is run. cheers Dan