You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
(9) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(2) |
Nov
(3) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2003 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
(1) |
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
|
|
|
From: Michel <mic...@io...> - 2002-07-08 16:45:55
|
[ CC: to the phpautodoc development list ] On Sun, 2002-07-07 at 23:39, Stephane wrote: >=20 > I discovered phpautodoc with your email. > Of course, I'm interesting to exchange ideas on > the releationship between phpdocgen and > phpautodoc. > But because phpdocgen is written in Perl > and phpautodoc seems to be written in PHP, > I think they must have separated lifes. :) What phpautodoc needs most badly IMO is a better parser. perl might be better for that, but I don't know if there's a reasonable way to mix PHP and perl. And I'd hate to reimplement all of it in perl because the code serves as an example for the inline documentation like this. > Perhaps we can study the support of the same > documentation syntax for the two tools. > Currently, the release 0.2 of phpdocgen > proposes a good set of tags. See > http://www.arakhne.org/tools/phpdocgen.php > for more details. That's indeed quite an impressive list, but it seems to me a lot of those tags simply aren't needed with phpautodoc because it retrieves the information automatically. --=20 Michel D=E4nzer | Iogram AG | http://iogram.ch Laupenstrasse 1 | 3008 Bern | +41 (0)1 465 45 45 |