Re: phpdoc problem
| From: | Sven Herrmann | Date: | Wed, 23 Oct 2002 14:15:36 +0000 |
| Subject: | Re: phpdoc problem | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-2535@lists.php.net to get a copy of this message | ||
Hello,
I've just had the same problem.
The error seems only then to occur if there's no other command in front of
the doc comment.
If I write a
require_once 'head.inc.php'
at the top of the file, everything's fine.
But this is a bug of PHPDoc, isn't it?
Greetings,
Sven
"Adam Morton" <adam@tux.appstate.edu> schrieb im Newsbeitrag
news:45927.152.10.114.75.1034617932.squirrel@tux.appstate.edu...
>
> I'm using phpdoc to document my own code and I've run into a little snag.
> When commenting in a class file and using the correct @package markup I
> recieve this error:
>
> PHPDoc is confused: module files must not contain classes. Doc will
> probably be broken, module gets ignored.
>
> I'm not using the @module markup in the file and the class is not placed
> under the package I specified. I followed the syntax given on pear.php.net
> and found in pear source files. I couldn't find any documentation on the
> heirarachy, nor what constitutes a module or a package. Any help here
> would be appreciated.
>
> Adam
>
> ---------------------------------
> Adam Morton
> Developer - Web Technology Group
> Appalachian State University
> http://phpwebsite.appstate.edu
>
>