*** CODING STYLE ***

To keep something easily readable, coders have to follow a same coding style.
Currently we haven't got much rules.

/*********************************************************************/

Keeping the brackets on a same column
	function ($var) 
	  {
		if (1 != 0) 
		  {
		 	print 'a';
		  }	
	  }


/*********************************************************************/

Use # comment character, to have something uniform with all scripts, shell
perl and PHP.


/*********************************************************************/

Always set $GLOBALS[sys_debug_where] when you start a fonction, like this

	$GLOBALS[sys_debug_where] = __FILE__.':'.__LINE__.':function_name';

Where function_name is replaced by the real name of the function.


/*********************************************************************/

Not mixing different languages. It means that <?php ?> can occurs only
one time in a file. If you need to print some HTML, use print();


/*********************************************************************/

Use only double-quotes for require statements

require "../include/pre.php";


/*********************************************************************/


Use easily 'grepable' tags in the comments like DEPRECATED: or FIXME: 


/*********************************************************************/


Providing feedback on top of the page is the better way to return feedback
to user. It means that actions must fed the $feedback variable and ideally
all these actions should be done _before_ the page header function call.

Feedback messages should be more or less similar, you should use the function
fb() (aliases: utils_feedback(), feedback())
	fb(_("Bla bla bla"));

For error messages should, the second argument of this function should be 
set to , something like
	fb(_("Bla failed due to crappy coding"), 1);

Finally, if you want to add debugging messages, do it using dbg() 
(aliases: utils_debug(), debug()), like
	dbg("This action before of this");

$GLOBALS[sys_debug_on] should be set to true, you want this function to be
effective.


/*********************************************************************/

Providing help about specific words is something nice to. It should be used
using help() (alias: utils_help())

	help(_("My sentence with words unclear"),
		array(	
		      _("sentence")=>_("sentence is ...")
		     ));



/*********************************************************************/


Savannah i18nized, do not insert strings without call to the gettext
"_()" function. And do not insert html tags inside (use printf/sprintf
if you need to put variables inside the gettext function.



...
