1 |
Id prefer to see something like |
2 |
#/// |
3 |
#/ |
4 |
#/ |
5 |
#/ |
6 |
#/// |
7 |
|
8 |
that is, each line that goes into documenetation has a prepending |
9 |
character, so that It is easy to tell it apart without folding, |
10 |
|
11 |
then again, maybe it doesnt need to be told apart... |
12 |
|
13 |
or a more in depth one, something like |
14 |
#///<documentation> |
15 |
#///<feature> |
16 |
#///<name>feature name</name> |
17 |
#///<description>a short description of the problem</description> |
18 |
#///<paramater>a paramater that could be passed to it</parameter> |
19 |
#///</feature> |
20 |
#///<feature> |
21 |
same as before... |
22 |
#///</docuementation> |
23 |
|
24 |
that way all documentation can just be extracted as xml... making |
25 |
parsing to a web page, or a man page, or whatever, a lot easier IMO |
26 |
|
27 |
(yes, this was stolen shamelessly from .net's documentation standards :)) |
28 |
|
29 |
|
30 |
On Sat, 27 Nov 2004 03:03:52 +0900, Georgi Georgiev <chutz@×××.net> wrote: |
31 |
> maillog: 26/11/2004-10:17:34(+0000): Ciaran McCreesh types |
32 |
> |
33 |
> |
34 |
> > On Fri, 26 Nov 2004 11:25:10 +0900 Georgi Georgiev <chutz@×××.net> |
35 |
> > wrote: |
36 |
> > | maillog: 25/11/2004-19:19:27(+0000): Ed Grimm types |
37 |
> > | > On Thu, 25 Nov 2004, Georgi Georgiev wrote: |
38 |
> > | > |
39 |
> > | > If you really think that in-line docs are ugly, use vim(1), and |
40 |
> > | > automagically fold them out of your view (:help foldexpr, although |
41 |
> > | > this can be set to happen in the eclass syntax file). I suspect |
42 |
> > | > that most of the people who only occasionally work with the |
43 |
> > | > eclasses, and those who are just starting to use the eclasses, would |
44 |
> > | > find them more useful than ugly. |
45 |
> > | |
46 |
> > | I have nothing against in-line docs in general. I simply had trouble |
47 |
> > | imagining it in the bash case. |
48 |
> > | |
49 |
> > | What about using perldoc itself? Simply prepend every doc line with a |
50 |
> > | '#', then run |
51 |
> > | |
52 |
> > | awk '/^#/ { sub("#",""); print } |
53 |
> > |
54 |
> > In bash? How would that work? |
55 |
> |
56 |
> I imagined |
57 |
> |
58 |
> #=item blah blah |
59 |
> # more POD |
60 |
> # and more |
61 |
> # and more |
62 |
> #=cut |
63 |
> |
64 |
> > Here's another possibility: |
65 |
> > |
66 |
> > # {{{ doc |
67 |
> > # whatever format we decide upon |
68 |
> > # blah blah blah |
69 |
> > # }}} |
70 |
> > |
71 |
> > Doesn't screw up normal comments, really easy to find and process, easy |
72 |
> > to turn into folds in the editor :) |
73 |
> |
74 |
> Sounds great. Now all that's left is to agree upon the format and write |
75 |
> the converter. Oh, and my favorite -- a GLEP maybe? (no, I'm not |
76 |
> sarcastic; just in a good mood ;) ). |
77 |
> |
78 |
> -- |
79 |
> ) Georgi Georgiev ) Hi! I'm Larry. This is my brother Bob, and ) |
80 |
> ( chutz@×××.net ( this is my other brother Jimbo. We thought ( |
81 |
> ) +81(90)6266-1163 ) you might like to know the names of your ) |
82 |
> ( ------------------- ( assailants. ( |
83 |
> |
84 |
> |
85 |
> |
86 |
|
87 |
-- |
88 |
gentoo-dev@g.o mailing list |