Code style guidelines #35
Labels
context/native
type/documentation
Improvements or additions to documentation
type/enhancement
New feature or request
Milestone
It's easy enough to follow the implicit style set by the existing C++ code, but we should probably explicitly set some convention guidelines for C++ just as we do for C#.
Also, do we have any guidelines in mind for what kinds of functionality should go approximately where on the managed side after bindings are made? In #34 I'd like to add something that actually calls the
Root::Quit()
binding, but I'm (as of writing this) honestly not entirely sure where it should go (Common or Engine, etc). It'll probably happen again, so it would be nice to have rough ideas for the futureThe text was updated successfully, but these errors were encountered: