Skip to content

Latest commit

 

History

History
119 lines (81 loc) · 4.04 KB

README.md

File metadata and controls

119 lines (81 loc) · 4.04 KB

C-Plus

alt text

C-Plus is an middle ground between c and c++.

It attempts to merge the cleanness low-levelness, and over all efficiency of c with higher level abstraction.

Although C-Plus supports objects [via structures with functions] it does not support OOP directly and does not plan to ever support OOP directly.

Build statuses

cplus workflow cplus workflow windows cplus workflow windows

building

to build the cplus compiler, simply run `make`

you can also very easily compile cplus by hand by running

`[your c compiler (ex. gcc)] main.c -o cplus`

installing

to install cplus, simply move cplus into your bin directory, on unix you can do this just by running `sudo make install` or `sudo mv cplus /usr/bin`

to install cplus on windows however, you must move cplus into the same directory that your c-compiler executable file is in

Supported Features

  • structs can be used normally without typedef
  • structs can be used as a class, i.e. the usr can define functions inside structs

externally defined functions use the same syntax as c++

ex.

void type::func(){

}
  • namespace, namespace syntax is slightly different than c++'s in that it uses . [optionally] instead of ::

ex.

namespace ns {
    int a;
}

int main() {
    ns.a = 5;
    ns::a = 5; /* this still works but it's ugly :) */
}
  • c+ header file support, via #import
    in order to load a c+ header file you must use #import
    import doesn't require you to specify if it's a global or local header\

ex.

#import header.hp
or
#import "header.hp" /* these do the same thing since the quotes are removed when parsed */

on unix systems (linux, macos, bsd, ect) c+ global header files are stored in /usr/include/c+

on non-unix systems (i.e, windows) c+ global header files are stored in ../include/c+\ I highly suggest windows users to put the cplus compiler in the same directory where their c compiler is stored

  • specify alt c+ header folder via #hpath

hpath allows the user to specify an alternative path to look for c-plus header files in

ex.

#hpath "../include"
#include "header.hp" 

standard c features that are not supported yet

  • multi-line pre-processors
  • embeded structs ~
  • compiling from multiple sources

Future Features

  • allow class functions to directly edit the values of a struct w/o this->
  • void*/casting object functions
  • load object using data (eg. char*)
  • operator overloading
  • embeded namespaces
  • string switches
  • typedef class carries over class functions
  • allow direct stucture managment in class functions (without this->)

(read TODO for more info)

Sili

The C-Plus compiler uses the Sili Toolchain for handling strings, arrays and file I/O

Sili helps to make C feel more modern and high level. Unlike many other higher level Toolchain/Standard Libraries [such as the c++ standard library]. Sili also makes sure the library doesn't just feel nice to use, it also runs efficiently.

Not does Sili modernize C while staying efficient, it is also very lightweight and is all contained in one small single-header-file.

This is why C-Plus uses sili for compiling and why C-Plus ships with sili and uses it as the official C-Plus Standard Library.

Copyright

The language design of c-plus (conversion to c, basic design, etc) is 100% public domain.

This means you can make your own c-plus compiler if you wish to. In fact, I encourage that you do if you're interested.

However,

The source code for this project (main.c) is copyrighted under the libpng license

this pretty much means you can use the code as you please so long as you don't pretend you wrote the original code, state any changes you made and keep all the copyright info attached