[docs] xmldocs - docelic modified 3 files

[docs at icdevgroup.org]

User:      docelic
Date:      2005-08-29 19:19:12 GMT
Modified:  bin      refs-autogen stattree
Modified:  guides   programming-style.xml
Log:
Little fixes and updates sitting on this machine the whole summer

Revision  Changes    Path
1.90      +1 -1      xmldocs/bin/refs-autogen


rev 1.90, prev_rev 1.89
Index: refs-autogen
===================================================================
RCS file: /var/cvs/xmldocs/bin/refs-autogen,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -r1.89 -r1.90
--- refs-autogen	9 Aug 2005 17:01:01 -0000	1.89
+++ refs-autogen	29 Aug 2005 19:19:12 -0000	1.90
@@ -288,7 +288,7 @@
 
 				@{ $$ag{'_directive type'} } = ("Global directive");
 				# For config directives, we can't simply do as above because catconf
-				# would then overrides globconf, and that's not okay! (We need to
+				# would then override globconf, and that's not okay! (We need to
 				# preserve the source contexts from globconfs, so we must handle
 				# this with some brains in the process).
 				# Here's what we do:



1.42      +4 -4      xmldocs/bin/stattree


rev 1.42, prev_rev 1.41
Index: stattree
===================================================================
RCS file: /var/cvs/xmldocs/bin/stattree,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- stattree	9 Aug 2005 17:01:01 -0000	1.41
+++ stattree	29 Aug 2005 19:19:12 -0000	1.42
@@ -858,7 +858,7 @@
 
 # This is basically an excersize in bracket-matching
 sub file_extractSub {
-	my ( $tagname, $func, $c, $context_data) = @_;
+	my ( $funcname, $func, $c, $context_data) = @_;
 
 	my $done = 0;
 	$func or die "file_extractSub with no args?\n";
@@ -877,7 +877,7 @@
 		my $line = $fc[$i];
 
 		if ( $line =~ /^\*$func = \\\&(\S+);/ ) {
-			push @{ $resolver_path{$$context_data{group}}{$tagname} }, {
+			push @{ $resolver_path{$$context_data{group}}{$funcname} }, {
 				name => $func,
 				file => "lib/$path",
 				lnum => $start,
@@ -887,7 +887,7 @@
 				ctx_n => 0,
 				ctx => [ format_ctx($line) ],
 			};
-			file_extractSub( $tagname, $1, $c, $context_data);
+			file_extractSub( $funcname, $1, $c, $context_data);
 			return;
 
 		} elsif ( $line =~ /^sub $func \{/ ) {
@@ -915,7 +915,7 @@
 
 	# func in lib/$path from $start to $end
 	$content = join '', @content;
-	push @{ $resolver_path{$$context_data{group}}{$tagname} }, {
+	push @{ $resolver_path{$$context_data{group}}{$funcname} }, {
 		name => $func,
 		file => "lib/$path",
 		lnum => $start,



1.5       +17 -0     xmldocs/guides/programming-style.xml


rev 1.5, prev_rev 1.4
Index: programming-style.xml
===================================================================
RCS file: /var/cvs/xmldocs/guides/programming-style.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- programming-style.xml	24 May 2005 21:42:18 -0000	1.4
+++ programming-style.xml	29 Aug 2005 19:19:12 -0000	1.5
@@ -252,6 +252,23 @@
   ) {
 ]]></programlisting>
 		</para></listitem>
+		<listitem><para>
+		Do not break blocks of code that obviously follow a lexical pattern.
+		For example, do not introduce double quotes or structural changes 
+		to the below:
+<programlisting><![CDATA[
+  ['FormAction',		 'action',			 ''],
+  ['MaxServers',       'integer',          10],
+  ['GlobalSub',		 'subroutine',       ''],
+  ['Database',		 'database',         ''],
+  ['FullUrl',			 'yesno',            'No'],
+  ['Locale',			 'locale',            ''],
+  ['HitCount',		 'yesno',            'No'],
+  ['IpHead',			 'yesno',            'No'],
+  ['IpQuad',			 'integer',          '1'],
+  ['TagDir',      	 'root_dir_array', 	 'code'],
+]]></programlisting>
+		</para></listitem>
 	</itemizedlist>
 </sect1>