Skip to content

Conversation

@suffisme
Copy link

Here added the code for printing and traversing the tree level wise and printing each level in the new line.

README.md Outdated
- [*Level order
traversal*](https://www.geeksforgeeks.org/level-order-tree-traversal/)
- [*Level order traversal*](https://www.geeksforgeeks.org/level-order-tree-traversal/)
- [Source Code](res/Tree/Tree_Level_Printing.cpp)
Copy link
Owner

@Nabagata Nabagata Oct 19, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rename it to 'Level order printing' in the readme @suffisme

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank You for suggestion.
It is done and i m sending you a PR.
Please review

Copy link
Owner

@Nabagata Nabagata left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Follow this naming convention:

C++ code

  • Use CamelCase for all names. Start types (such as classes, structs, and typedefs) with a capital letter, other names (functions, variables) with a lowercase letter. You may use an all-lowercase name with underscores if your class closely resembles an external construct (e.g., a standard library construct) named that way.
  • C++ interfaces are named with an Interface suffix and abstract base classes with an Abstract prefix.
  • Member variables are named with a trailing underscore.
  • Accessors for a variable foo_ are named foo() and setFoo().
  • Global variables are named with a g_ prefix.
  • Static class variables are named with a s_ prefix.
  • Global constants are often named with a c_ prefix.
  • If the main responsibility of a file is to implement a particular class, then the name of the file should match that class, except for possible abbreviations to avoid repetition in file names (e.g., if all classes within a module start with the module name, omitting or abbreviating the module name is OK). Currently, all source file names are lowercase, but this casing difference should be the only difference.
  • The rationale for the trailing underscore and the global/static prefixes is that it is immediately clear whether a variable referenced in a method is local to the function or has a wider scope, improving the readability of the code.

@Nabagata
Copy link
Owner

@suffisme can you pull the latest changes in the master branch in your branch and then rename the filenames like Level wise Tree Traversal to levelWiseTreeTraversal? I'll merge once you do the renaming

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants