ACS File Naming and Formatting Standards

Prev	Chapter 11. Engineering Standards	Next

By Michael Yoon and Aurelius Prochazka

+ACS File Naming and Formatting Standards

Prev	Chapter 12. Engineering Standards	Next

ACS File Naming and Formatting Standards

By Michael Yoon and Aurelius Prochazka

OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.

@@ -95,7 +95,7 @@ This can be at the top or bottom of the file.

Using ad_page_contract

For non-library Tcl files (those not in the private Tcl directory), -use ad_page_contract +use ad_page_contract after the file path comment (this supersedes set_the_usual_form_variables and ad_return_complaint). Here is an example of using ad_page_contract, which serves both documentation and page input @@ -141,7 +141,7 @@ set_the_usual_form_variables. The use of bind variables makes such previous variable syntax obsolete.

Using ad_library

-For shared Tcl library files, use ad_library after +For shared Tcl library files, use ad_library after the file path comment. Its only argument is a doc_string in the standard (javadoc-style) format, like ad_page_contract. Don't forget to put the @cvs-id in