Incorrect return types(`void` is appended) about doc-en HOT 6 CLOSED

It happens :)

from doc-en.

@haszi seems like the type linking change broke something php/phd@45cffd6

from doc-en.

@haszi seems like the type linking change broke something php/phd@45cffd6

@Girgias Oof. I just took a quick look and it seems that there is a large number of doc files with this kind of format:

<methodsynopsis>
 <type>void</type><methodname>apache_child_terminate</methodname>
 <void/>
</methodsynopsis>

with the first <type>void</type> being all kinds of types in the different methods/functions. While this seems incorrect to me (what do the two voids each represent? One is the return type and the other...), there are over a thousand files like this.

I'll only have time to take a closer look tonight (in 5-6 hours) so if this is urgent, please revert that change and I'll think of a way to suppress the superfluous <void/> elements (and I'll also make a script to remove these from the docs, if you agree).

Also, type linking seems to add .html at the end of the links which doesn't work, so I'll have to remove those too. It was working on my machine ™️

from doc-en.

The </void> means that the function has no parameters the return type is always before the function name even if it is void :)

from doc-en.

The </void> means that the function has no parameters the return type is always before the function name even if it is void :)

Of course... What an epic screwup! :-( I don't know how I missed something this obvious but I'll fix this tonight.

from doc-en.

Thank you for fixing it :)

from doc-en.