ANTIRIGHT HACKING GUIDELINES

All applicable code should follow GNU C style.  

All code must be written either C, bourne shell, awk, or sed.  C++ code is not 
to be inserted into any of the antiright core components.  This may change in 
the future, but it is most likely that it will not.  

Changes are to be recorded on cvs checkin.  

Code should produce no warnings when compiled with GNU gcc using the -Wall and 
-W flags. 

No linking in of new external libraries without my permission is allowed.  
This is simply to ensure the small footprint of the AntiRight Desktop 
Environment.  

Only one argument to a function is to be given per line, with the exception of sets such as coordinates and resource-value pairs.

Spaces are to be left around operators.

Assertions must contain a statement producting a boolean result.  Do not just pass a variable, unless it is boolean.

Certain naming conventions are to be followed:
Global variables and functions are to begin with the prefix antiright_ or ar_.  If the function or variable is in a client application, the client's name may be used as the prefix, such as arcd_play or xmtextedit_print_cb.
New variables should be defined as follows:  The type and whether or not the variable is a pointer should be the suffix.  All should be in lowercase unless a constant is being defined.   Such is as follows:  
    antiright_form_widget, antiright_label_xmstring, antiright_title_char_string
Shortcut and old style suffixes may also be used:
	int		_value
	double		_value
	XmString	_motif_string
	char*		_string
	Boolean		_flag
	XtCallbackProc	_cb

