You can either pronounce it as two-pee-see-see or two pieces.

⚠ The development is temporarily suspended due to lack of knowledge in parsers.

Notice: this compiler IS NOT compliant with the ANSI C standard. Some things break compliancy by choice, all the others do so by mistake. Of course I don't know all the ANSI C standard draft by memory.

Typically, making an executable file out of source code involves a compiler, which translates the source code into object code, and a linker, which links the object code with prospective libraries. 2pcc takes a different approach: it divides the job into platform-dependent and platform-independent, so that every part does roughly the same amount of work. This allows each part to focus on one job only and therefore achieve simplicity. Platform-independent work is done by a representer while platform-dependent work is done by a realizer.

The 2pcc linker also attempts to statically link shared libraries, so that it is not necessary to build them again. Why? Because dynamic linking was a mistake.

You can find some documentation in the doc directory.

☑ = present, tested and working.
☒ = missing, not tested or not working.

• ☒ Line reconstruction
• ☒ Preprocessor
• ☒ Checks and replacements
  • ☒ Type replacement
  • ☒ Automatic type casting (optional)
  • ☒ Expression validity check
• ☒ Optimization (optional)
• ☒ IR code generation
• ☒ UTF-8 support
• ☒ Language extensions
  • ☒ Embeddable structures (Go-like composition)
• ☒ Command line utilities

Each realizer has its own roadmap since its development is platform-dependent.

• Simplicity
• Lightness
• Minimalism

• Complexity
• Heavyweight features
• Extreme code optimization

2pcc is licensed under the Creative Commons Zero (CC0) license.

Attribution is not required by the Creative Commons Zero license. However, I'm happy if you give me credit for my work :)