Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117250 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 13640 invoked from network); 3 Mar 2022 17:09:43 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 3 Mar 2022 17:09:43 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5A997180545 for ; Thu, 3 Mar 2022 10:31:30 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) X-Envelope-From: Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (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, 3 Mar 2022 10:31:29 -0800 (PST) Received: by mail-lj1-f180.google.com with SMTP id y24so7890345ljh.11 for ; Thu, 03 Mar 2022 10:31:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dqxtech-net.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4ewi0++4n0uw8GlfdsZC+OheeHFJcleC+xBJZGxAWBc=; b=fknbuFIaDxQKMBSf9bFQu0exWqv10FP2Kj9RuNqkkULa//4tOG7fpmfeOeWDssqima o1YcuDAHU3CUfzCHBg/zrLlXFKwccb5Ca3g7P6NT02klEFr3oLa+nHzZ9AVcEAMqsXNh LulqtR/2R9B8I+x9wde8fHZRDOtf0dyoSLurIRlYy73gOoQq2YR3Z/ii9MBF/yWUfygf u8sUVFA7DUGV3kmOq04+mb5a3GnGYQ5VKHH7+1DmWfcRt/WdY6k7g0ORL/SnNV64cGA8 EWNWZR8HTBm5S9SQVGFe0bGoRyaFpOhiLIfRlzYEti7tUrOUUhGz6/dVunSewxkrkvpg FK/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4ewi0++4n0uw8GlfdsZC+OheeHFJcleC+xBJZGxAWBc=; b=c2ZjvcsCYJeHQIYPN+O3QoHlzrPhegxt8m3wW5A5VS6fgjrF33Xj+MvYOrD5AK9Eme nWBF/MsRMViocYYXLMtwLVoq79Yg0grMRjLGg9HX2HuYsxebVllaS0aIVb8aMuxUi/Gl W4CyOlJy5hkvK3oET/MS9GAwgqwkbgjTgxQUb/czlthYpwulbRCag1aUaWrje57VNsiE aBjJscMdOQ6P4+KpuJVKiPZzheq4bIZluWqqQJa8mwY5a3u6WRxPFD9eVAx+pm7Nw34g uwNnqGX+7YWt4q1O4sZqT1EBjjMg8H0OsSySc89p7gJVTuMF27h/JXgst1Bd0+PSutOh wCig== X-Gm-Message-State: AOAM533mqkk8GraoGQjhIhCCcM1h0j+WdpjZty8KeG6lo0IDgtS5F2qj k8fls10gDzXMViLdLcHNspmB5MOvUQHXLaqYF3OW6g== X-Google-Smtp-Source: ABdhPJxHkH1Jhzu83bMLAYrJ90dpwGMFhOw4AM+AHiFtcsPs1LTlHBzMaxkcZ0FYgNZLtwngvBGSj7eaNPqaOqsvpS4= X-Received: by 2002:a05:651c:199f:b0:246:89bc:b95d with SMTP id bx31-20020a05651c199f00b0024689bcb95dmr14240940ljb.321.1646332288101; Thu, 03 Mar 2022 10:31:28 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 3 Mar 2022 19:31:16 +0100 Message-ID: To: DANIEL VARGAS MUCCILLO Cc: Larry Garfield , php internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] Interface for reflection entities who implements getAttributes method From: andreas@dqxtech.net (Andreas Hennings) On Tue, 1 Mar 2022 at 21:03, DANIEL VARGAS MUCCILLO wrote: > > > > > I *think* all Reflector children support attributes, so it may not need a > > separate interface. > > > ReflectionZendExtension and ReflectionExtension are currently the only ones > who implement Reflector but don't support attributes. There is also ReflectionAttribute itself which does not have getAttributes(). > > > > However, the entire Reflection class hierarchy is a mess and needs a > > number of additional interfaces added to it generally. It makes sense to > > overhaul it holistically to make sure it all fits together. > > > > Was not aware of other cases, but a quick look led to: > > - getExecutingFile() : string and getExecutingLine() : int in > ReflectionFiber and ReflectionGenerator; > - getDocComment() : string|false in ReflectionClass, > ReflectionClassConstant, ReflectionFunctionAbastract and ReflectionProperty; > - getName(), getNameSpaceName() and getModifiers() in some cases (not > always together). > > Should it be the case to expand the scope to handle these in the same > proposal or maybe create a Meta RFC and discuss each on their own? > > > > I have zero availability until mid-March, but I'm open to helping at that > > point. > > > Thanks for your return on that, I'll try to run at least a little on my own > foot until there, so I can be less of a burden! > > -- > Daniel Vargas Muccillo