Comment
by project member
jackokring,
Oct 27, 2011
This project is under slow development, and was inspired by the idea of developing a Java for Tiny Core Linux. The small class library idea is something I am developing anyhow, for my own Java and android projects. It is not a Java compiler. It is a .jar file converter, and threaded code execution engine. It requires the use of a simple class library, and so is not SE, ME or ANDROID, but a new class library, for which an SE, ME or ANDROID implementation layer could be written, and is being written. As such not all features will be supported.
Softhardware and Unconditionaly Stable Binaries are not described in this documentation, but they are the most profound advertisement Title. Please explain this Softhardware and Unconditionaly Stable Binaries, from comp.arch ! I like he Title, but the documentation is void(). Hi http://jarvar.googlecode.com as a new take on the purpose of Java style syntax and security, versus the hobby, bytecode, opcode hardware, driver, chipset paradigm. CheersJacko? ;)
Comment
by project member
jackokring,
Nov 21, 2011
I have reached a nice point in the design. The primitives seem to have complete coverage for general computation, and may be added to for efficiency. The foundation API contains enough classes to be able to design simple programs. The function API is as yet, un-evolved. I'm thinking about this, with the goal of keeping it simple.
Comment
by project member
jackokring,
Mar 26, 2012
The current idea being factored into the design is a massively parallel user scripting environment using Google App Engine. I must look into it. The general idea is to have a keyword multi which makes a variable totally global, and arrayed. The return of Critical copies, and updates via fetch a Critical and update yourself locally, seems best for isolation security. The keyword maybe user can index into the state space.
Good progress. I may remove Box from the Java classes, and use Func instead, as this simplifies some things. I renamed the SL verb word to does. I'll also make true and false print in full, but as true does not have to be the same as another true, some information is lost when converting back to text. The idea of all truths being not the same, except the ones which logically have to be is a potentially useful feature. Maybe this is when pattern matching gets added.
This project is under slow development, and was inspired by the idea of developing a Java for Tiny Core Linux. The small class library idea is something I am developing anyhow, for my own Java and android projects. It is not a Java compiler. It is a .jar file converter, and threaded code execution engine. It requires the use of a simple class library, and so is not SE, ME or ANDROID, but a new class library, for which an SE, ME or ANDROID implementation layer could be written, and is being written. As such not all features will be supported.
The class and interface basis is considered to have enough coverage. The methods and ScriptLanguage is now being considered.
Softhardware and Unconditionaly Stable Binaries are not described in this documentation, but they are the most profound advertisement Title. Please explain this Softhardware and Unconditionaly Stable Binaries, from comp.arch ! I like he Title, but the documentation is void(). Hi http://jarvar.googlecode.com as a new take on the purpose of Java style syntax and security, versus the hobby, bytecode, opcode hardware, driver, chipset paradigm. CheersJacko? ;)
I have reached a nice point in the design. The primitives seem to have complete coverage for general computation, and may be added to for efficiency. The foundation API contains enough classes to be able to design simple programs. The function API is as yet, un-evolved. I'm thinking about this, with the goal of keeping it simple.
The current idea being factored into the design is a massively parallel user scripting environment using Google App Engine. I must look into it. The general idea is to have a keyword multi which makes a variable totally global, and arrayed. The return of Critical copies, and updates via fetch a Critical and update yourself locally, seems best for isolation security. The keyword maybe user can index into the state space.
Good progress. I may remove Box from the Java classes, and use Func instead, as this simplifies some things. I renamed the SL verb word to does. I'll also make true and false print in full, but as true does not have to be the same as another true, some information is lost when converting back to text. The idea of all truths being not the same, except the ones which logically have to be is a potentially useful feature. Maybe this is when pattern matching gets added.