The Portable Forth Environment implements the ANSI Standard of the Forth programming language. It is fully written in C, and with gcc the virtual machine can be put into cpu registers. The newer development versions implement a set of modern features including modularization and multithreading. The terminal connection itself can be configured to work in an embedded environment.
ZZIPlib provides read access on ZIP-archives. The library uses only the patent-free compression-algorithms supported by zlib. Functions are provided that transparently access files being either real files or zipped files, both with the same filepath. The zip-archive can be used in the place of a normal subdirectory. It is written in portable C.
gstdint.h installs a header file, "gstdint.h", that will "#include" the "stdint.h" or "inttypes.h" header file of the local system - if one of these exists. Otherwise the bitsizes of basic types are detected for the local libc/compiler pair, and the C96 inttypes typedefs are generated into "gstdint.h".
mksite.sh is a static Web site / project HTML documentation formatter that only requires the Bourne shell and sed. It gives a common look and full navigation to an HTML Web site along with all the needed metadata detection, site map generation, and variable expansion. It has a tabbed layout suitable for hundreds of Web pages, and is small enough to be added to any project tarball.
As the discussion went, I think that betting on a parrot or some kind of multi-language approach is a false excuse. As already said, in a multi-developer environment there will be a standardization on source style even going beyond basic syntax elements. Anyway, there is a saying that for some new technology to find a breakthrough it needs to have *two* additional useful features over existing ones. And sure it does not make it easier to add some pain to the mix like some syntax that looks familiar but which means a different thing now. So there is still the argument why to do such a thing when one can have just as well a feature upgrade on the good ol' stuff.
Re: What's the probem exactly?
Using "int" instead of "long" is another problem, see also discussions about
"64bit and data size neutrality".