Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66588
Return-Path: <kalle.php@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 59117 invoked from network); 11 Mar 2013 14:39:41 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 11 Mar 2013 14:39:41 -0000
Authentication-Results: pb1.pair.com header.from=kalle.php@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=kalle.php@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender)
X-PHP-List-Original-Sender: kalle.php@gmail.com
X-Host-Fingerprint: 209.85.217.170 mail-lb0-f170.google.com  
Received: from [209.85.217.170] ([209.85.217.170:60632] helo=mail-lb0-f170.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id D8/41-52104-CACED315 for <internals@lists.php.net>; Mon, 11 Mar 2013 09:39:41 -0500
Received: by mail-lb0-f170.google.com with SMTP id ge1so3201275lbb.15
        for <internals@lists.php.net>; Mon, 11 Mar 2013 07:39:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:references:mime-version:in-reply-to:content-type
         :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date
         :to;
        bh=2DqR4bgx57wDYdtFZ6WVAkRhvPZSfGL8CuozrikxP6w=;
        b=avQjomJBvB+fBJ319rpck+R3YJZJ8TWRZR61u48kgjMJBB/gkA8AXEGqnpw4mpkIJP
         PvxPZOsXJPFcc0inTjao+0vgNWrwIPRlHMYpsoHc5biR3C1nZpY9WcANavYrA1QmG6b0
         2uxqP9IrwOlGDAnCg3gKQvzkipBL780Xz5Hw97NMdM6+Z056IIn+LO8NnhmHxnm2ey0q
         SHY/gSwLCtjYgadSBPnLMAIlxUregAZq2sOd2zrjWmro2pBvnvaI4csNTm0+O3HvQO6k
         U1gkvAT5rVFBnujiw3hH7NJ5H0YYcgcDoDViP4HlLfCLENKY01+oqtc8FtKzo/eRg+Or
         3fQA==
X-Received: by 10.112.42.37 with SMTP id k5mr4673684lbl.49.1363012777322;
        Mon, 11 Mar 2013 07:39:37 -0700 (PDT)
Received: from [192.168.1.13] (2-106-203-140-dynamic.dk.customer.tdc.net. [2.106.203.140])
        by mx.google.com with ESMTPS id e9sm4581978lbz.1.2013.03.11.07.39.35
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Mon, 11 Mar 2013 07:39:36 -0700 (PDT)
References: <513DBDD4.3010804@gmail.com> <513DCBBF.8020809@gmail.com> <513DD458.7040705@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <513DD458.7040705@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-ID: <424385FE-682A-4CD0-98D5-B067D9EE2F75@gmail.com>
Cc: =?utf-8?Q?=C3=81ngel_Gonz=C3=A1lez?= <keisial@gmail.com>,
 "internals@lists.php.net" <internals@lists.php.net>
X-Mailer: iPhone Mail (10B146)
Date: Mon, 11 Mar 2013 15:39:32 +0100
To: Eric James Michael Ritz <lobbyjones@gmail.com>
Subject: Re: [PHP-DEV] Double-Colon Always Follows the 'parent' Keyword?
From: kalle.php@gmail.com (Kalle Sommer Nielsen)

Hi

Den 11/03/2013 kl. 13.55 skrev Eric James Michael Ritz <lobbyjones@gmail.com=
>:
>=20
> Thanks for the idea.  Checking for brackets would work but not
> whitespace since PHP allows programmers to write code such as
>=20
>    echo $this->  parent;        // Same as $this->

Technically "parent" and "self" is not keywords, they are implemented as T_S=
TRING. These are only used as keywords when the next non whitespace token is=
 a double colon, like:

self::$property->...

So I would continue reading until the next token and decide from there if it=
s used in a "keyword-context" or not to decide its syntax highlight color.

-K