Remove security framework

The framework has never been fully implemented and is not used
by anone. Remove it from the code to simplify things. In the future
it might be implemented in a different way.

2013-01-23  Gwenael Casaccio <gwenael.casaccio@gmail.com>

	* kernel/Behavior.st: Remove security.
	* kernel/BindingDict.st: Remove security.
	* kernel/Class.st: Remove security.
	* kernel/ContextPart.st: Remove security.
	* kernel/Metaclass.st: Remove security.
	* kernel/Object.st: Remove security.
	* kernel/Security.st: Delete the file.
	* kernel/SysExcept.st: Remove security exceptions.
	* libgst/Makefile.am: Remove security files.
	* libgst/comp.c: Remove security checks.
	* libgst/dict.c: Update Class structure.
	* libgst/dict.h: Update Class structure.
	* libgst/files.c: Remove security file from bootstrap.
	* libgst/gst-parse.c: Remove security checks.
	* libgst/interp.c: Remove security checks.
	* libgst/opt.c: Remove security checks.
	* libgst/prims.def: Remove security primitives.
	* libgst/security.c: Remove file.
	* libgst/security.h: Remove file.
	* libgst/sym.c: Remove security checks.
	* packages.xml: Remove security file.
	* packages/stinst/parser/STSymTable.st: Remove security checks.
	* tests/Makefile.am: Remove security tests.
	* tests/testsuite.at: Remove security tests.
	* tests/untrusted.ok: Remove security tests.
	* tests/untrusted.st: Remove security tests.

VisualGST
2013-01-29  Holger Hans Peter Freyther  <holger@freyther.de>

	* Notification/Kernel/Metaclass.st: Remove usages of #isUntrusted
	and #makeUntrusted:
stinst: Export comments in way they are parsable with pharo 1.4

Add >>#fileOutComment:to: to the FileOutExporter and re-implement it
for Squeak/Pharo to write it as a chunk. This is confirmed working with
Pharo 1.4.

2013-01-29  Holger Hans Peter Freyther  <holger@freyther.de>

	* Exporter.st: Add FileOutExporter class>>#fileOutComment:to:.
	* SqueakExporter.st: Re-implement the
	SqueakSyntaxExporter class>>#fileOutComment:to: using chunks.
stinst: Put the class variables into the classVars and not the pool

The class variables were placed in the pool and not the class variables
array. This was found while exporting OsmoLogging to Squeak syntax.

2013-01-29  Holger Hans Peter Freyther  <holger@freyther.de>

	* tests/stcompiler.st: Add parsing test.
	* tests/stcompiler.ok: Update the test result.

2013-01-29  Holger Hans Peter Freyther  <holger@freyther.de>

	* STLoaderObjs.st: Put class variables into the classVars array.