[docs] xmldocs - docelic modified 4 files

docs at icdevgroup.org docs at icdevgroup.org
Tue Mar 1 05:31:13 EST 2005


User:      docelic
Date:      2005-03-01 10:31:12 GMT
Modified:  bin      stattree
Modified:  guides   programming-style.xml
Modified:  refs     NoCache
Added:     refs     DomainTail
Log:
- bin/stattree:
 - some comments
 - small extension for the future to support a more complex
   source context reports

- guides/programming-style.xml:
 - small improvement of efficiency in an example

- refs/NoCache:
 - reverted back the content that I accidentally removed

- refs/DomainTail: new

Revision  Changes    Path
1.39      +7 -9      xmldocs/bin/stattree


rev 1.39, prev_rev 1.38
Index: stattree
===================================================================
RCS file: /var/cvs/xmldocs/bin/stattree,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- stattree	8 Feb 2005 10:23:30 -0000	1.38
+++ stattree	1 Mar 2005 10:31:12 -0000	1.39
@@ -38,7 +38,8 @@
 my $ctx_p = 10; # How much context lines to show before
 my $ctx_n = 4; #                                after
 my %resolver_path; # Support for stack (a -> b -> c -> d   =>
-                   # a = d with full "path" recorded). This expands MapRoutines.
+                   # a = d with full "path" recorded). This expands
+                   # MapRoutines, parse_ functions and things like that.
 
 # All file types should be listed here or the stats wont be accurate.
 # It should be reported if an unknown file is found in the archive (you can 
@@ -451,8 +452,8 @@
 				};
 
 				# Push whole resolved chain; last item is actual function
-				if ( $resolver_path{$tagname} ) {
-					while ( my $spath = shift @{ $resolver_path{$tagname} } ) {
+				if ( $resolver_path{$c{fsubtype}}{$tagname} ) {
+					while (my $spath=shift @{ $resolver_path{$c{fsubtype}}{$tagname}}){
 						push @{ $hash{symbols}{$c{fsubtype}}{$tagname} }, {
 							ctxpre => 0,
 							ctxpost => 0,
@@ -818,10 +819,7 @@
 
 # This is basically an excersize in bracket-matching
 sub file_extractSub {
-	my $tagname = shift;
-	my $func = shift;
-	my $c = shift;
-	my $context_data = shift;
+	my ( $tagname, $func, $c, $context_data) = @_;
 
 	my $done = 0;
 	$func or die "file_extractSub with no args?\n";
@@ -840,7 +838,7 @@
 		my $line = $fc[$i];
 
 		if ( $line =~ /^\*$func = \\\&(\S+);/ ) {
-			push @{ $resolver_path{$tagname} }, {
+			push @{ $resolver_path{$$context_data{group}}{$tagname} }, {
 				name => $func,
 				file => "lib/$path",
 				lnum => $start,
@@ -875,7 +873,7 @@
 
 	# func in lib/$path from $start to $end
 	$content = join '', @content;
-	push @{ $resolver_path{$tagname} }, {
+	push @{ $resolver_path{$$context_data{group}}{$tagname} }, {
 		name => $func,
 		file => "lib/$path",
 		lnum => $start,



1.3       +5 -7      xmldocs/guides/programming-style.xml


rev 1.3, prev_rev 1.2
Index: programming-style.xml
===================================================================
RCS file: /var/cvs/xmldocs/guides/programming-style.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- programming-style.xml	3 Feb 2005 15:30:36 -0000	1.2
+++ programming-style.xml	1 Mar 2005 10:31:12 -0000	1.3
@@ -104,13 +104,11 @@
 		Lining up <literal>=</literal>s in a series of assignments can be
 		used to emphasize the parallel structure.
 <programlisting><![CDATA[
-sub init_calc {
-#::logDebug("reset_state=$Vend::Calc_reset init_state=$Vend::Calc_initialized -- initting calc from " . caller);
-	reset_calc() unless $Vend::Calc_reset;
-	$CGI_array  = \%CGI::values_array;
-	$CGI        = \%CGI::values;
-	$Carts      = $::Carts;
-	$Items      = $Vend::Items;
+    reset_calc() unless $Vend::Calc_reset;
+    $CGI_array  = \%CGI::values_array;
+    $CGI        = \%CGI::values;
+    $Carts      = $::Carts;
+    $Items      = $Vend::Items;
 ]]></programlisting>
 	</para></listitem>
 



1.4       +31 -1     xmldocs/refs/NoCache


rev 1.4, prev_rev 1.3
Index: NoCache
===================================================================
RCS file: /var/cvs/xmldocs/refs/NoCache,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- NoCache	22 Feb 2005 12:50:43 -0000	1.3
+++ NoCache	1 Mar 2005 10:31:12 -0000	1.4
@@ -1,3 +1,33 @@
 __NAME__ purpose
-(obsolete)
+(obsolete) explicitly specify pages or directories that are not to be cached when static page building is enabled
 __END__
+
+
+__NAME__ synopsis
+<group choice='req'>
+	<arg choice='plain' rep='repeat'>file or directory name</arg>
+</group>
+__END__
+
+__NAME__ see also
+Static, StaticAll, StaticDepth, StaticDir, StaticPath, StaticPattern,
+StaticIndex, StaticLogged, StaticPage, StaticDBM, StaticFly, 
+StaticSessionDefault, StaticSuffix, StaticTrack
+__END__
+
+
+__NAME__ description
+The directive lists names of &IC; pages that are not to be built statically
+if &glos-static; page building is in use. If the name is a directory, no
+pages in that directory (or any below it) will be cached or built statically.
+__END__
+
+
+__NAME__ example: Setting NoCache
+Put the following in &ccf;:
+<programlisting>
+NoCache ord special
+</programlisting>
+__END__
+
+



1.1                  xmldocs/refs/DomainTail


rev 1.1, prev_rev 1.0
Index: DomainTail
===================================================================
__NAME__ purpose
only honor the toplevel domain in IP qualification
__END__


__NAME__ see also
DomainTail,IpHead,IpQuad,WideOpen
__END__


__NAME__ synopsis
<group choice='req'>
	<arg choice='plain'>yes</arg>
	<arg choice='plain'>no</arg>
</group>
__END__


__NAME__ description
The directive simply specifies that only the toplevel domain 
should be used in IP qualification for &glos-session; IDs.
If, for example, an IP was <literal>ri01-053.dialin.iskon.hr</literal>,
only <literal>iskon.hr</literal> would be used.
__END__

TODO: how does this work with non-resolving stuff?

__NAME__ notes
This directive is a compromise on security, but it allows browsers that
do not accept cookies to use multiple proxy servers in the same domain.
Note that this directive is <emphasis role='bold'>enabled</emphasis>
by default.
</para><para>
If you are encrypting credit cards with PGP/GPG or using payment services
(such as CyberCash), then look at the &conf-WideOpen; directive, which
enables more browser compatibility, again at the cost of some more security.
__END__

__NAME__ example: Disabling DomainTail
<programlisting>
DomainTail No
</programlisting>
__END__









More information about the docs mailing list