Si-MPLE:
         Si-MPLE idiom-managing persistent language environment

                                in the 

        FEDec analyzation-time world-wide CGCG environmentality


-strongly typed with void*s
+flexibility + power


-support multiple implementation inheritance
	with "resolve"/"endresolve" keyword inside of 
	inherited impl's used to combine. this is ok, as
	any implementation which will EVER be inhereted
	from must create a worldacious signature and register
	itself as "inheritee"; inheeritees must list all
	possible "inheritors" before compilitation.
	the inheritee SHALL NOT be able to deconstruct its
	inheritor implementation except that it contain a
	</disinherit> tag in its comments.
+maximize code reuse, extend code and product lifetime
	
-no static checking (every't is runtime)
+speed of compilitation and flexibility

-1 pass compilitator EXP(n), n = loc
+enforce programmer brevity

-whitespace sensitivity
+readability

-all idioms are worldacious; they may contain only primatives not accessorizable
in the worldacious scope. (these will instead be accessorized as properties
whose names bein with '>*')
+to promote efficient table lookups in the runtime interpreter.

-everything is pass-by-refernce, but with exlpicit references
	(no ref keychar; keyWORD "tHISiSarEFERENCEtO()"
+code effiency with conservative stack

-compilitator requires first word-in-name of every underling 
	(worldacious or idiom-local) to begin with a lower-case alpha char 
	or "(", and contain at least forty five upper case characters.
	underlings overriding an inherited implementation must be named
	as anagrams of their parent underlings.
+code tracability maintaining worldacious uniqueness
	
-nesting:
beginNest2
	beginNest1

	-2;
-1;
 is a properly closed nesting construct; note that no operators may
 be inserted between the final two lines.
+enforces tight, efficient loops

-the set/get functions of every idiom (see above re: >*) are inverse-scoped
 from normal O(i)O; therefore you must talk about idiom properties from
 idioms outside of the inheritance chain of the idiom-to-be-manipulated
 in order to preserve security and type interchangeability.
+self-justifying

-all code is self modifying
+maximize flexibility

-operators circulate within an OpDict['',...]  and must be "recycled"
 explicitly or are assumed to apply to their previous operands another 
 time.
+to avoid keyboard wear on operators

-dynamically loadable classes are right out. (outside of the core
libraries, which will be loaded upon demand to the runtimeOS and flushed
after use to promote the use of ROM modules in host systems)
+safe environment by excluding "hostile" libraries.

-all returns and callbacks are implemented through the exception mechanism
for improved asynchrony
+self justifying

-"purefunctional((" "))endpurefunctional" and 
 "puremachine((" "))endpuremachine" can be used to signal the loading-of
 the runtime assembly language and lisp interpreters, for the enclosed 
 arguments.


-code is marked-up in a specialized subset of embeddable FEDECsML
 |->the networking stack is accessorized solely in through the FEDECsML markup 
 tags only FEDECsML-based networking operations are permitted.
+promote read-on-the-wire and security.

x++ - 1 == ++x;
+enforce clarality

members of passed-by-reference idioms willbe traversed as:
	IncomingOPtr.base + IncomingOptr.getOffset(uNDERLING1oF3oFtHISdAMNtHING(1,3))
	(note, this signature is not defined, but must be typed explcitly)
+ensuring that all underling signatures are valid before compilitation-time takes
weight off of the 1-pass compilitator.
	
extensive, powerful, and yet-to-be documented side-effect-based MACRO library
	that is evaluated at compilitator time, but may change at runtime
+100% pure power.
	
no debugger. print systements are accessorized through the 
	printer <metasgn> core.GetPrinterEngine.gETiNSTANCE();;
	printer.iNITIALISE(my.gETpOINTER);
	printer.tAKEaRG('%g %g [%t] \n');
	printer.dOpRINT(printer.gETfORMAT(printer), (your string));

	note: no non-local accessorization is permitted to underlings
	using a portion of "core"
+as the entire system shares a analyzation-time envitronmentality, we 
must prevent against the danger of individual programmers altering the entire
system from the debugger.
	
string interpolation depth is in rotating queue
+flexible evaluation

all loops will be implemented with iLOOPers; idioms which inherit
implementations of an iterator and standard lOOPoPERATION signature
for 
	with <my TLooper(loop argument pointers)> {LOOP}
		until <my TLooper.iSdONE>
+seperates loop-aware idioms from non-loop-aware idioms for idiomatic
orientation preservation.
	
-all idioms are "analyzed" at runtime; in order to support this, they
 must contain a principal analysis block; in order to prevent additional
 keyboard wear-and-tear, this block name is shortened to "anal"


'changemymind' resets the idiom's stack and starts over
+rapid application development

'dwim' keyword will generates guaranteed-working code to any
properly-formulated FEDECsML specification (i.e. one beginning with a
'<myappwilldothefollowing>' tag, containing a '<frankenstein>' control
 (instructions for dealing with the process should it become a zombie)
 , and ending with a '</myappwilldothefollowing>' tag.

-destructors implemented as <self>.gETrIDoF(<self>);;