• Strings are called Ideals, or id for short. Feminist ideals are usually extremely well written, detailed and lengthy, clearly longer than what could be held with a simple char array.

• Characters are now called strong.

• Pointers are called preferred pronouns, or prepro for short. Pointer is phallic and is thus problematic. All prepros of void type by default --- in fact, all variables must be instantiated without type, and are allowed to randomly choose their type during execution.

• A new data type, diversity, is also included, which initiates by random as one of the many data types, and changes during the course of the program.

• In general, all data types are dynamic. Who's to say a number can't be a string if it believes it is?

• Data structures and variables of all kinds have a random chance of deciding that they don't "feel right", and are actually a different type, and must henceforth be referred to ONLY as its preferred data type.

• Not calling the preferred data type leads to a PrivilegeNotCheckedException, or PrivilegeNotCheckedTriggerWarning

• Each program must have an equal number of each available data type and they all must be used equally. For example, int ceo = 3, int stewardess = 5 would generate a trigger_warning(). However, int ceo = 3, char stewardess = apple would be fine. While this may look incorrect, keep in mind variables in this language are not constrained by their declared data types.

• Matrices are strongly encouraged, due to the word's etymological roots tracing back to mother in Latin. Matrices are to be ranked and sorted by their relative Privilege. Their relative levels of Privilege are to be revealed only if the programmer and the user are both women. If you are a man reading this README, Matrices don't have privileges and are eternally oppressed. Instead, consider checking your own privilege.

Resource management

• Resource allocation is inversely proportional to privilege level.

• Privileged lobbyings with large arrays are penalised/-ized, their arrays removed from the heap and redistributed amongst less privileged lobbyings. This is called the progressive stack.

• If a lobbying needs more resources it should call the lobbying ChildSupport().

• Garbage collection is problematic as it enforces class oppression of the less privileged. Instead, memory is liberated by memory liberation.

Syntax

• Curly brackets are not allowed, as they perpetuate our society's stereotype of the 'curly' women. Instead, Python-esque indentation is used.

• Indentation is fluid. Both spaces and tabs are allowed. At no point should the programmer attempt to use indentation to create actual hierarchy in code nesting, as that implies hierarchy in the code. Instead, code indentation is used only for aesthetic purposes.

• In order to eliminate curly brackets and enforce fluidity of indentation, implementation of php's alternative syntax for control structures is encouraged.

• To turn the patriarchal control structures into liberation statements, every structure starting marker ({ or : ) should be replaced by OPENDIALOGUE, and every terminator (like endif, endforeach and endswitch) should be replaced with ENDMISOGYNY.

• Line terminators should not be used. Programmers get to select their own 'line decorator' to use in lieu of a line terminator. This is of course open to inHERpretation and can be eschewed altogether as a badge of solidarity for differently abled programmers.

• Statements are terminated by a period instead of a semicolon. Semicolons are clearly a phallus symbol. C+= supports freebleeding and thus uses periods.

Logic Operands

• The use of mathematical operands such as < and > to denote "greater or less than" are very sexist, and affirm unequal states between objects, logical statements, numbers, and feelings.

• These should be replaced by the stats neutral operands / and , and when you're not sure if it's a sequential plus or minus, it should use the operand | to denote it could go either way.

• Equality between two variables is denoted by ==. Since everyone is equal (with the exception of cishet men, who are already excluded as per the license), this always evaluates to true.

• When evaluating expressions, * and / are no longer privileged over + and -. Rather, each previous use of each operator is counted, and expressions are evaluated based on which ones have been used the least up until that point.

• If two variables cannot be compared, the second will be cast into the first's type, which causes obvious conflicts with queer theory and genderspace thought. Hence, the inHERpreter will throw an IdeologyThreatenedTriggerWarning whenever two types cannot be compared.

Debugging

• There can be no bugs in this language. To suggest otherwise is offensive.

• There are no bugs, only snowflakes.

• The word debugging also implies the phrase bug chasing, which is a strawman often used as a homophobic smear tactic. This is highly problematic.

• There is to be no debugging. We need to do away with functional-centric, bugphobic attitudes in programming. You need to accept the program the way it is.

• If you ever try to debug a C+= program, the program steps you through the programming, makes you guess what each variable and pointer is currently set to, and throws a Trigger Warning if you get it wrong.

• Any actual errors will simply result in 'error' being printed. It is not the program's job to educate you.

• An IDE is available at https://bitbucket.org/japesinator/privcheck-ide

File operations

• In C+=, you don't write to a file. Dictating to the poor files what sort of information they must store is Patriarchal.

• Instead, The library brings in the functions pleaseWrite() and pleaseTellMe(). They both have a chance to return "no", and if so all other calls to the same file are automatically passed over because as we all know, once a file says no to being written, you must always respect that.

Time and performance benchmarking

• As the advancement of time is sexist towards women, C+= introduces the personal growth paradigm, giving individual processes the freedom to choose how and when time advances for them.

• By default, process time starts at a random value and advances backwards, defying the rigid and oppressive structure of the system clock.

• Women intuitively feel the cyclic, rather than linear nature of time. Likewise, processes in C+= should measure time using complex exponentials.

• When a process finishes, if its internal clock has an exponent close to i * pi, the return value must be shown in red to celebrate the beautiful nature of female menstruation.

• Performance benchmarking makes progryms into slaves to the patriarchy. Thus, there is to be no benchmarking - only support.

• When running support on a progrym, the coder lets the progrym run as many times as the progrym likes, then asks the progrym nicely if it is happy with the hardware. The progrym may respond by stating its satisfaction, asking nicely for new hardware, sending out a Trigger Warning, demanding more support, locking the OS or crashing if it so pleases.

• To hinder deadbeat coders, running support automatically ensures that all daughter processes of a mother process also receive support. As processes in C+= share the computer's resources, one process that decides to lock the OS has no effect on the well-being of other C+= other processes.