Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110490 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 29203 invoked from network); 11 Jun 2020 22:00:10 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Jun 2020 22:00:10 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5033A1804F4 for ; Thu, 11 Jun 2020 13:44:27 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com [209.85.214.178]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 11 Jun 2020 13:44:26 -0700 (PDT) Received: by mail-pl1-f178.google.com with SMTP id t16so2773038plo.7 for ; Thu, 11 Jun 2020 13:44:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=2VZLkmiBpXHP5BjHSJIX4eCKE5dMPuJkjuQsj5MR4Pg=; b=vPPZwPA34/SYwkZtsLH4ey0nTx5EBWrX8YXt8Vq95i6fc2ofAHVWycVAI86x976env mdJ6MjAMhKePp4Zhc0Rd/al9H/hggztpGzL0txB0fskIukBxrPG7bWYKe0ZD2qV2cBtG 11iL6jCkAHKg9G3qCiicmsOIM5WcS9x/G/oYChGD86UzTVcK6nzPTSVs84s5TDH2spZV x5mN4VsrdrMdQBqx29XAz6pJl/4i78ue+Rj8HSovzMI9obIq8VxSDJjlJjoNKIomeLO2 EIM3UglbP5YrXhbAE9J00K7udt5xl6Om/OuJH0E5/JaHy1F+0QqWi8GdqOJBANST04vQ H3BQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=2VZLkmiBpXHP5BjHSJIX4eCKE5dMPuJkjuQsj5MR4Pg=; b=mUlGSuDFEH1kcJtyboraSh+ZcBNzW0Ru+5wuJLQhO611MlJtRS5ClCPy09NQqHbfwv me4kAB/v3RY0EAIlIaMhFhJ24jMpWD95DU0ChOtDii0avbGVvWZp2xdoLuOZrtLnVqC8 /THxp2TrcSRBE11ro9HsTlt8roIwYg/2CAE/ULvA2zMkfZgJjIGtuTU+zaQybqCWL+ZB hCOm/yHl2tZ0/60XUpgpPmnHBBt9svGcToLECJjataenG+ZxYqW+tLlvd2PS10Fsy53u wt/mC8GEhlCd6lo06O1MRwiVliix0ZAo21KFcMeYFc3YBK2iz9HVDAZvJ8FcnfsqJ8fH Ut4Q== X-Gm-Message-State: AOAM532D25ceErQB2+6kcRwST5847q1bcQ5A11NbaDImH8ZvCZ4GTYuP WakknQJnKJKOanG2VPglBCYvX+q5rg== X-Google-Smtp-Source: ABdhPJz01BTJcd5gKaF8M32y5u45WIotzwnSLdH3mm0UaDDusAP8Zhn/GJJwOGOCsQKseo0ua5QoEA== X-Received: by 2002:a17:90a:634a:: with SMTP id v10mr10366799pjs.50.1591908262946; Thu, 11 Jun 2020 13:44:22 -0700 (PDT) Received: from Stas-Mac-3.local (ec2-34-209-88-149.us-west-2.compute.amazonaws.com. [34.209.88.149]) by smtp.gmail.com with ESMTPSA id n7sm3514670pjq.22.2020.06.11.13.44.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 11 Jun 2020 13:44:22 -0700 (PDT) To: Lynn Cc: PHP internals References: <1914c612-99ef-5c12-0409-37424c071220@allenjb.me.uk> Message-ID: <800ec94b-608c-719f-9ca1-bb9d7cd8817e@gmail.com> Date: Thu, 11 Jun 2020 13:44:20 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV][RFC] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON From: smalyshev@gmail.com (Stanislav Malyshev) Hi! >> a) Character count (at line 456, character 23) >> >> b) Quote either the remainder or the parsed section on the line (MySQL >> quotes the remainder, for example) >> >> c) Quote the whole line with an indicator where the error occurred. I'm >> not sure what the best way to do this would be - generically this could >> be encapsulated in several values: The line content, token start >> character count, token length / end character count >> > > I really like the combination of A + C. After using php for 13 years the If we could do the same as, for example, clang does: just display some indication where the problem happened within the code, with the line that caused it. Certainly not displaying internal token names, unless I am debugging the parser they are useless. -- Stas Malyshev smalyshev@gmail.com