CoreUtilities - LeFreq/Singularity GitHub Wiki

Since this project realized the dreams of OOP, objects get re-used across many applications. This means that commonly-used objects can stay resident in memory (like shared memory system), or even in cache. Bigger components and apps fork in directions from common core objects, but even many of these will get re-used (like a HTML renderer, for example).

So what are some core objects that would get re-used? A String object which implores inputs to be binary in range of 1 byte, and promises to output IBM ASCII codes, for example. A TextFile object which implores bytes and promises a EOF at the end. Running this object would print the contents to STDOUT. textfile >> Printer would print the input file.

//NewObject = (OldObject1,OldObject2), (1,2,2,1)

Core utilities that are provided by the system itself:

1. test(Object); #Object
2. run(Object); 1/Object
3. help(Object); ?Object
4. clone(Object); %Object
5. >> Object; send(Object)
6. << Object; getfrom(Object)

The language must distinguish between data and functions within a module. Objects (in an OOP language) are data + functions.

File is to data and functions as an Object is to data and functions in a different dimension of order, from the order of STORAGE to the "order" of PROCESSING. file:(data,functions)::Object:{data,functions}

//Thought: is it necessary to have a "class ClassName(): ..." if you can "ClassName() = {...}"? yes.