www.phpdoc.org is down

[scholz.lothar]

I tried to get PHPDocumentator but the website is down for days.
I find it strange that the server of such an important tool does not
get more attention.

Or is there an alternative i missed.

How important is PHPDocumentator? And why is it not added to the
standard php distribution?

[J2Be.com]

<sc***********@gmail.comha scritto nel messaggio
news:7e**********************************@c36g2000 prc.googlegroups.com...

I tried to get PHPDocumentator but the website is down for days.
I find it strange that the server of such an important tool does not
get more attention.

Or is there an alternative i missed.

How important is PHPDocumentator? And why is it not added to the
standard php distribution?

Yes, it seems to be down.
I suppose that you can find it here:
http://pear.php.net/package/PhpDocumentor

It's not possible to Include EVERYTHING that you thing is useful within php,
you can always add things by yourself and create your own packages including
wathever you need, even recompile php itself and integrate pecl extensions.
So it's up to you to create something that will satisfy entirely your needs.
For example a good thing for debugging php is xdebug but it doesn't mean
that MUST
be included in php. We should also think about the fact that most projects
are mad by third
parties and could not always be included in the main projects and It's
better to have a slim
version of php that we can amplify via pecl modules and/or php
classes/frameworks/etc.

The standard php distribution is good as is, maybe we can suggest what could
be useless :) and removed
from the main distribution.

In any case there are different opinions regarding those arguments and
there's no a real solution
and in most case things are added if the developers receive alot of requests
from the users or if
there are commercial/marketing/diffusion incentives, for example the mysql
(and other dbms) support in php have been a good choice for the diffusion of
php.

Regards

L. A. Iarrusso

[Curtis]

sc***********@gmail.com wrote:

>Yes, it seems to be down.
I suppose that you can find it here:http://pear.php.net/package/PhpDocumentor

Unfortunately this is only the source code pear package, not the
documentation
manual. I think i wait month and hope it comes up.

>It's not possible to Include EVERYTHING that you thing is useful within php,

No not everything. But a standardized source code documentation
style should be defined in PHP. Hope that i don't need to discuss
that this is an essential part of language. This _MUST_ be
standardized and maintained by the core team.

(Fixed word wrapping.)

Although tools like pydoc and javadoc are pretty handy, their use is
not required nor necessarily prerequisite to good documentation.
Regardless of the tool you use to document your software, you still
have to be thorough and complete.

Developers are free to document their software however they see fit,
there is no "one-size-fits-all" standard for documenting projects.

[FUD snipped]

--
Curtis
$eMail = str_replace('sig.invalid', 'gmail.com', $from);

[Rik Wasmus]

On Fri, 31 Oct 2008 21:42:32 +0100, <sc***********@gmail.comwrote:

>Yes, it seems to be down.
I suppose that you can find it
here:http://pear.php.net/package/PhpDocumentor

Unfortunately this is only the source code pear package, not the
documentation
manual. I think i wait month and hope it comes up.

Erm, look at:
http://pear.php.net/package/PhpDocum...anual.pkg.html
--
Rik

[scholz.lothar]

On 31 Okt., 23:06, Curtis <[e-mail]:

Although tools like pydoc and javadoc are pretty handy, their use is
not required nor necessarily prerequisite to good documentation.
Regardless of the tool you use to document your software, you still
have to be thorough and complete.

The problem cames when you look at libraries not applications.
Libraries used by many people. Especially libraries that some day move
into the base distribution. Here we need one and only one style.
And since you never know what happens in the future, be prepared
all the time.

Developers are free to document their software however they see fit,
there is no "one-size-fits-all" standard for documenting projects.

Well i'm really tired to hear this nonsense. There is the need to do a
well
known how do document. You still have enough freedom it's a
"one-fundamental-to-customize-all".

[FUD snipped]

Unfortunately it wasn't FUD, if you think that the development style
of
PHP is in any way acceptable you are as intelligent as a female vice
president.
By the way: It will not help to wait a month. The site was definitely
sold
to a "PHP Doctor". Interesting question is where to get the stuff now.
Not the PEAR
package but the whole cake.

[Evil Otto]

On Nov 1, 10:00*am, [e-mail] wrote:

On 31 Okt., 23:06, Curtis <[e-mail]:

Although tools like pydoc and javadoc are pretty handy, their use is
not required nor necessarily prerequisite to good documentation.
Regardless of the tool you use to document your software, you still
have to be thorough and complete.

The problem cames when you look at libraries not applications.
Libraries used by many people. Especially libraries that some day move
into the base distribution. Here we need one and only one style.
And since you never know what happens in the future, be prepared
all the time.

Developers are free to document their software however they see fit,
there is no "one-size-fits-all" standard for documenting projects.

Well i'm really tired to hear this nonsense. There is the need to do a
well
known how do document. You still have enough freedom it's a
"one-fundamental-to-customize-all".

[FUD snipped]

Unfortunately it wasn't FUD, if you think that the development style
of
PHP is in any way acceptable you are as intelligent as a female vice
president.

By the way: It will not help to wait a month. The site was definitely
sold
to a "PHP Doctor". Interesting question is where to get the stuff now.
Not the PEAR
package but the whole cake.

I think you might find that you get more help from the people in this
group if you modify your attitude. Everyone's development style is
different, and what works for me doesn't necessarily work for you and
vice versa. I agree that documentation is important, and most people
would agree, but insisting that you know the One True Way to develop
is counter-productive at best.

Adding extensions isn't rocket science, and most Linux distros come
with at least some packages that add extensions to PHP.