- how to get attention for a possible bug, report now years old

Hi, Years ago I reported what I thought should be fairly simple to resolve. The issue number (below) is that now the zend code goes through the following logic # test 1 #define __restrict__ restrict later test #2 # define __restrict__ And always: #define restrict __restrict__ In this case: test #1 is done by the OS include files, and test#2 and the final assignment are done in zend*.h (was zend.h, now zend_portability.h) As I do not really *know* the importance of the *restrict* and/or *__restrict__* keywords, maybe this is less important than spilled milk. My idea for a patch was to not do test 2 if __restrict__ was already defined. However, what is the value, or sense of the result - which would be: #define __restrict__ restrict #define restrict __restrict__ It feels like a bug - it certainly confuses me. M p.s. https://bugs.php.net/bug.php?id=62346