A prototype is a preliminary model of something. Projects that offer physical products need to show backers documentation of a working prototype. This gallery features photos, videos, and other visual documentation that will give backers a sense of what’s been accomplished so far and what’s left to do. Though the development process can vary for each project, these are the stages we typically see:
Proof of Concept
Explorations that test ideas and functionality.
Demonstrates the functionality of the final product, but looks different.
Looks like the final product, but is not functional.
Appearance and function match the final product, but is made with different manufacturing methods.
Appearance, function, and manufacturing methods match the final product.
[ NOTE: you can turn on English subtitles in the video above ]
[ NOTE: the video in the gallery, that is a walkthrough of the compiler might not maximize nicely on all computers or tablets, the video is also available on YouTube at: https://youtu.be/hTqMKpXGJX4 it maximizes nicely from there ]
COOGL (pronounced "see-oogl" as in "see ogly eyed bird ogling at you") www.COOGL.org
Help us, with your support, to complete the implementation of the compiler for the COOGL programming language.
We want to raise at least $100K to fund one senior compiler writer for 6 months (originally planned to be done by November, but this phase will be ending around end of February). This will produce a late beta level compiler. If we raise up to around $300K we would hire a second engineer to work with the first one for 6 additional months to complete the compiler into a GA 1.0 version together with ports to various platforms, larger test suite, etc.
The large majority of the world's system software infrastructure is written in C or in C++. Software at risk from the unsafe nature of C and C++ includes: operating systems, virtual machine hypervisors, database servers, transaction monitors, application servers, web servers, file servers, backup systems, compilers, run-time systems, industrial control systems, web browsers, networking infrastructure, security, authentication, encryption, and a large number of applications built on top of these technologies, even if those applications are written in safe languages.
A few safe, or safer, programming languages, such as C#, Java, Eiffel, and Go, are used at the higher levels of application programming, but the core infrastructure continues to be written primarily in C or C++. The gap between C and C++ and these other languages is large, causing large bodies of system software to continue to be maintained and enhanced in C and C++ instead of being rewritten in safe languages. The fundamental problem with those safe languages is that their memory management approach, through mandatory garbage collection, and their memory safety approach, through an extremely tight type system, makes their use inappropriate as an evolutionary path for existing C and C++ code.
As the world's dependence on information systems continues to grow, it is important that an evolutionary path exist for these systems to be reengineered, incrementally, into systems that are safer through the use of a safe programming language for system software, COOGL is that language. COOGL is very close to C, but safe, it is not garbage collected.
The book that describes the language is available free online, see www.COOGL.org, and the compiler will be released under an open source license.
Risks and challenges
At this time the grammar for the language has been specified, a book that describes the language has been written, and the implementation of the compiler for COOGL is about 40% complete. A flex and bison based compiler with actions to create the parse tree, pruning of the parse tree, symbol tables, entering of declarations into symbol table, various options to output the parse tree, declarations, and symbol tables have already been implemented. Code generation has been partially implemented. The compiler at this time is capable of syntactically validating COOGL programs.
The bulk of the work that remains involves type checking, code generation, run-time support libraries, test case development, and a few other miscellaneous items.
The language designer and the COOGL team need your support to continue to fund the COOGL R&D efforts. Without support from the community the development of COOGL can not be accelerated.
A tremendous amount of effort has already been invested into COOGL, this is open source technology, together with a forever free to download book that describes the language. It is meant to benefit humanity by enabling the evolution from unsafe infrastructure written in C/C++ into infrastructure written in COOGL.
We appreciate your support.
Learn about accountability on Kickstarter