[Autosec-devel] sonar/doc sonar_plugin_man.tex,1.1,1.2

[Jacob F. <ph...@us...>]

Update of /cvsroot/autosec/sonar/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv21213/doc

Modified Files:
	sonar_plugin_man.tex 
Log Message:
s/are/as/


Index: sonar_plugin_man.tex
===================================================================
RCS file: /cvsroot/autosec/sonar/doc/sonar_plugin_man.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** sonar_plugin_man.tex	8 Apr 2004 21:57:32 -0000	1.1
--- sonar_plugin_man.tex	12 Apr 2004 23:45:51 -0000	1.2
***************
*** 17,21 ****
  \chapter{Plugin Functions}
  Depending on what type of plugin you are writing, you must specify certain required functions and fill them in.
! Input, Output, and Networking plugins have different requirements that we will outline below. Because of the structure of sonar's plugin API, you need not name your functions are they are named below, and in fact, I encourage you to choose a more descriptive name for your functions.  However, you must provide a function that will perform the main task of the functions.  Each plugin is assumed to return PLUGIN\_OK on success if it has an \emph{int} return type. 
  \section{Input Plugins}
  \subsection{plugin\_open}
--- 17,23 ----
  \chapter{Plugin Functions}
  Depending on what type of plugin you are writing, you must specify certain required functions and fill them in.
! Input, Output, and Networking plugins have different requirements that we will
! outline below. Because of the structure of sonar's plugin API, you need not name
! your functions as they are named below, and in fact, I encourage you to choose a more descriptive name for your functions.  However, you must provide a function that will perform the main task of the functions.  Each plugin is assumed to return PLUGIN\_OK on success if it has an \emph{int} return type. 
  \section{Input Plugins}
  \subsection{plugin\_open}