| Re: Major trouble with PhpDocumentor [message #182313 is a reply to message #182312] |
Sun, 28 July 2013 02:22   |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 7/27/2013 10:14 PM, Fiver wrote:
> On 2013-07-28 03:38, Jerry Stuckle wrote:
>> What about the links on the phpdoc.org site ("Contact us", "Report a
>> bug", etc.)?
>>
>> When dealing with a product, the first place to go should be that
>> product's support structure. No one will know the product as well as
>> those who wrote it.
>
> Their support structure, as far as I can tell, is GitHub. I could file a
> new issue for every problem I encountered, sure, but that would a) swamp
> their bugtracker, and b) be premature until I can eliminate the
> possibility that I'm simply doing something wrong. I saw *so* many bugs
> that I need to rule out a systematic error on my part first. If they had
> a forum or mailing list, I would certainly try that first.
>
> I would also like to know what everybody else is doing to document their
> source code when they're using PHP 5.4 syntax. I find it hard to believe
> that I'm alone in this situation.
>
> Thanks,
> 5er
>
This still isn't a good place to ask such questions. I suspect very
few, if anyone, uses it. They also have a "Contact us" link you can
use. You might make a suggestion they add a forum. Or, if you can't
figure out if you're doing something wrong, start filing bug reports.
If the documentation is that unclear, maybe it needs to be fixed.
Personally, much of my code is documented before any code is written
(it's called a "design"). It may or may not be a complete design,
depending on the complexity of the project. But the rough outlines are
there. Then I add any additional details as I go along.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]