Index: openacs-4/packages/acs-api-browser/tcl/acs-api-documentation-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-api-browser/tcl/acs-api-documentation-procs.tcl,v diff -u -r1.30.2.4 -r1.30.2.5 --- openacs-4/packages/acs-api-browser/tcl/acs-api-documentation-procs.tcl 20 Sep 2015 15:40:15 -0000 1.30.2.4 +++ openacs-4/packages/acs-api-browser/tcl/acs-api-documentation-procs.tcl 9 Oct 2015 13:27:35 -0000 1.30.2.5 @@ -105,7 +105,7 @@ regsub -all {\#.*$} $line "" line set line [string trim $line] if { $line ne "" } { - set has_contract_p [regexp {(^ad_(page|include)_contract\s)|( initialize )|} $line] + set has_contract_p [regexp {(^ad_(page|include)_contract\s)|(Package initialize )} $line] break } } @@ -987,15 +987,15 @@ Given a proc name, formats it as HTML, including highlighting syntax in various colors and creating hyperlinks to other proc definitions.
The inspiration for this proc was the tcl2html script created by Jeff Hobbs. -

+

Known Issues: -

    -
  1. This proc will mistakenly highlight switch strings that look like commands as commands, etc. -
  2. There are many undocumented AOLserver commands including all of the commands added by modules. -
  3. When a proc inside a string has explicitly quoted arguments, they are not formatted. -
  4. regexp and regsub are hard to parse properly. E.g. If we use the start option, and we quote its argument, +
      +
    1. This proc will mistakenly highlight switch strings that look like commands as commands, etc. +
    2. There are many undocumented AOLserver commands including all of the commands added by modules. +
    3. When a proc inside a string has explicitly quoted arguments, they are not formatted. +
    4. regexp and regsub are hard to parse properly. E.g. If we use the start option, and we quote its argument, and we have an ugly regexp, then this code might highlight it incorrectly. -
    +
@author Jamie Rasmussen (jrasmuss@mle.ie)