> 1. using := instead of = is straigh up worse. No way i'd use 2 characters instead of 1 for an operator that common. Maybe you have mistaken := as the assign

> 1. using := instead of = is straigh up worse. No way i'd use 2 characters instead of 1 for an operator that common. Maybe you have mistaken := as the assign operator? It rather is for local variable declaration: foo := xy becomes auto foo = xy; so it's 2 characters instead of 7 :) > 2.i don't think the eventuality of bugs really justifies the repetition of public and private at EVERY SINGLE variable, that's a lot of repetitions Good point. My thinking was that Java/C# seem to be fine with that decision. Also the : after public/protected/private clashes with Coffee++'s Python-like scopes. > 4. (also a lot of other minor things that don't add meaning, like (int argc, char argv) that really shouldn't be there) The reason for keeping stuff like (int argc, char argv) is that I want this to be used in C++ projects in the sense that you could have some Coffee++ files and some C++ files together with the only difference, that your build system translates the Coffee++ files to C++ before compiling. But I'm open to replacing other annoyances of C++. Maybe int main(std::vector<std::string> foo): could be translated into int main(int argc, char** argv) { std::vector<std::string> foo; for (int i = 0; i < argc; ++i) { foo.emplace_back(argv[i]); } ;)