Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117185 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 5365 invoked from network); 1 Mar 2022 18:41:33 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 1 Mar 2022 18:41:33 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 921C2180505 for ; Tue, 1 Mar 2022 12:02:49 -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.8 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, 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: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) X-Envelope-From: Received: from mail-qv1-f50.google.com (mail-qv1-f50.google.com [209.85.219.50]) (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 ; Tue, 1 Mar 2022 12:02:48 -0800 (PST) Received: by mail-qv1-f50.google.com with SMTP id b12so1999199qvk.1 for ; Tue, 01 Mar 2022 12:02:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ufsm-br.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jbYH42KhdrDaJQi/XLgolP66ew92jbxXPTMbrcCuC+4=; b=yALtMJgzOnLJyecgBNlvTKd/RI6iPlJOCOSOyfzxJRND5xfJezF4SRH0Rknk+D4uBV JAz39DLjgODCXXW32Bgu8JKkjphnNZTukRXum2wqzNzudJwlBKEiuPnooLSRMEBRqwcW +Y0y/3hNCyDAqvHPTVPXm6Oq+nSyKl9f/TUUQGD0Qh4ab3kFxuDVylVHKUV0e0b10wRm V/O35WR6gpsLD7xRiQi8c/TuBgll0HC/ckzAMLHIaHS3uJ0A4bdhW6iCZWy9hkg8Strq kEkgp3q9qAB3Xr5uppWcjjn/YnjRWonoS+7uYfXowhh6fjcIPdmu/JsbYwIqo01+Ct0M VRLg== 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=jbYH42KhdrDaJQi/XLgolP66ew92jbxXPTMbrcCuC+4=; b=EcbH+WbktVMCXkCP7npxJg8mTdRQnEQjDAe4xAtvuL0NHV8AthI8jVSM4xsjnfJD/x vo/RYURoJLYuJrTXfL0V8Ul0fY72/qPRADB5zoruB/aqsOsFOrX+rnZVDNm9uswOn2jA P27rCMdaj5z8VuI0e+lI9Zg3J34gsxG8f5ZgIxLDV5FdOoqN1sWxdlg2+a7z6VHXQPk2 lXxkTcb9qpDGjRep3QPwjlQLmyEPQ2SUInjRIYrBLx2YKdZjsMMBSAF2qNQ6zRALkW8d mFdaUjJMENG6to6OVHaJSIE9s9xuGIYjx8Ra3bsqwdV6yB3nENwb25Z2kv35oi+9yMOm yYNg== X-Gm-Message-State: AOAM532r7Chb0qtmd1LDorFuzGf/gYasNjHKp0oMjUO0YDSAy+n2RNcg PNnD1QuqWh0gpUj9QZAfLmbzhVYuKxs+4GNauB226nRd8lk= X-Google-Smtp-Source: ABdhPJykpSLih7TIsjjwr/8g6Okm82a1Vw+EcCoq+E2TBFZ+JQwqQO9SBGRCzSxDvEhyJsCdscQinziEK7YBgFD2FkA= X-Received: by 2002:a05:6214:f2c:b0:432:dbb2:569f with SMTP id iw12-20020a0562140f2c00b00432dbb2569fmr13382788qvb.16.1646164968213; Tue, 01 Mar 2022 12:02:48 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 1 Mar 2022 17:02:37 -0300 Message-ID: To: Larry Garfield Cc: php internals Content-Type: multipart/alternative; boundary="0000000000002c20d805d92da6a8" Subject: Re: [PHP-DEV] Interface for reflection entities who implements getAttributes method From: daniel.muccillo@ufsm.br (DANIEL VARGAS MUCCILLO) --0000000000002c20d805d92da6a8 Content-Type: text/plain; charset="UTF-8" > > 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. > 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 --0000000000002c20d805d92da6a8--