Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help
ferite(1L)							    ferite(1L)

       ferite -	ferite programming lanugage command line tool

       ferite [options]	name_of_script [-- options to script]

       This  little program allows you to run a	ferite script from the command
       line.  It is particularily useful for testing scripts and  for  writing
       programs	that are not tied to another application.

       To get a	list of	options, use 'ferite --help'.

       The  ferite  options are	listed below.  In keeping with the freedom-of-
       choice philosophy, options may be eliminated or default	values	chosen
       at  compile-time, so options and	defaults listed	may not	accurately re-
       flect the version installed on your system.

	      Show the current for the program

	      Show the current version or the program

	      Show the current copyright for the program

	      This will	cause the ferite executable to be verbose, this	 means
	      that  it will explain where abouts in the	grand scheme of	things
	      it is, eg. loading a file, compiling it, deleting	it.

	      This will	cause the program to dump the list of arguments	it  is
	      passing to the initialisation of the ferite engine.

       -e script, --execute script
	      This will	cause ferite to	instead	of loading a disk file to com-
	      pile and run, use	the string script.     eg.   ferite  -e	 "uses
	      'console';  Console.println('Hello');"  -	 this  will  print out

	      ferite will only compile the program - this is useful for	check-
	      ing that you have	written	syntacically correct code

	      ferite  will  display  any  warnings that	are accumilated	whilst
	      compiling	or executing a script.

       -Ipath, --include path
	      This will	add path  to  the  list	 of  directories  that	ferite
	      searches for library files, this is useful if you	 are say test-
	      ing a library before installing it, or have particular paths for
	      files [eg. a home	directory].

       -Pmodule, --preload module
	      This will	add module to the list of modules that get loaded into
	      the system before	the script is compiled.

       The following options are specific to the engine	and can	be used	 where
       ever the	engine is used.

	      This  will  turn	on internal debugging of the engine. This will
	      (if the engine has been compiled with  --enable-debug)  cause  a
	      huge amount of data to be	outputed onto stdout.  The information
	      contained	within it is invaluable	- tracking of function	execu-
	      tion flow, all sorts of messages allowing	for the	very quick lo-
	      cation of	bugs.

	      ferite by	default	uses's it's  own  memory  suballocator	called
	      jedi  but	there are times	when it	is useful to either access the
	      system's malloc directly,	or to track when memory	is being used.
	      If ferite	is compiled with debugging, the	classic	memory manager
	      will track memory	allocations and	dump a table at	the end	of the
	      program's	execution to show all allocated	memory.	 This is vital
	      for tracking  memory  leaks.   WARNING:  This  mode  will	 cause
	      ferite's	speed  to drop immensily - it's	only useful for	debug-
	      ging the engine.

	      ferite keeps internal counters of	memory useage, use this	to see
	      at  the end of a programs	execution how much memory is still al-
	      located, or has been allocated.

	      Tell ferite to use it's own memory manager with the pcre regular
	      expression library

       Of  course! What	software project would be without bugs?	Please Please,
       email bug reports to - thanks.

       ferite is designed and implemented by Chris Ross	<>

       ferite Home Page	--
       Author's	Home Page --

Yeah!			  ferite programming language		    ferite(1L)


Want to link to this manual page? Use this URL:

home | help