You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browsing Friction's code reminds me that we should maybe adopt a code style for the project. I like how Inkscape does it:
Bumping the C++ version to something like C++17 or C++20 wouldn't hurt either.
#ifndef CATEGORY_CATEGORY_FILE_NAME_H
#definePRIVATE_DOCUMENT_H
#include"document.h"
#include<stdlib>
#include<QApplication>
#include"../canvas.h"
#include"../memory.h"namespaceFriction::Ui { // Two spaces between headers and code// No tab for namespacesclassWidget : publicSomething {
// People usually agree on 4 spaces, but I prefer something like 8// to avoid too much nestingpublic:Widget() {};
~Widget() = default;
};
}; // namespace Inkscape::UiWidget::Widget () {
if (aSpaceBetweenIsMoreReadable) {
return;
}
}
#endif// PRIVATE_DOCUMENT_H
Should we adopt a specific code style? Which one do you prefer?
Yes we should, but I don't know which one I prefer
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
@rodlie @pgilfernandez
Browsing Friction's code reminds me that we should maybe adopt a code style for the project. I like how Inkscape does it:
Bumping the C++ version to something like C++17 or C++20 wouldn't hurt either.
2 votes ·
Beta Was this translation helpful? Give feedback.
All reactions