An .clang-format file is provided. Write with POSIX-compatibility in mind and try to avoid Windows API functions as much as possible in order to reduce the number of #ifdefs.

Use PascalCase for structure names and camelCase for variable/function names.

You can always assume the latest compiler (Only gcc is supported, but clang should work most of the time). Use as much asserts as needed. (For example if malloc fails and there is no other way to save the program)

User-facing strings should be localized (Like in Messages), but not in exception messages. Tabs should be used and braces should be on the same line:

if(foo) {

}

instead of

if(foo)
{

}

You can always assume the latest java version, so you can use every feature of the language without any hesitations.

Until Java 17, the use of preview features is allowed (--enable-preview), after that, only normal, non-preview features should be used.

Add as many testcases as needed, if you add a new method. Write Javadoc for every new public class/method/constant. Always qualify a field-access or method-access with this:

public class Foo {
	private int foo;

	void a() {
		...
	}
	void b() {
		this.a();
		SomeExternalClass.method(this.foo);
	}
}

Encapsulate as much as possible and prefer the usage of Streams and Lambda-expressions over loops. Make sure that each method only has one responsibility.

The codestyle is currently quite ambiguous, but will be improved in the next weeks/months.

These should be sorted alphabetically (sort -o foo.properties foo.properties)