docs/v8_c_plus_plus_styleand_sops.md - Issue 1347153006: [Docs] Add wiki content to Markdown docs

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: docs/v8_c_plus_plus_styleand_sops.md

Issue 1347153006: [Docs] Add wiki content to Markdown docs (Closed) Base URL: https://chromium.googlesource.com/v8/v8.git@master

Patch Set: Created 5 years, 3 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

Index: docs/v8_c_plus_plus_styleand_sops.md

diff --git a/docs/v8_c_plus_plus_styleand_sops.md b/docs/v8_c_plus_plus_styleand_sops.md

new file mode 100644

index 0000000000000000000000000000000000000000..56865045439e54e7b1fb7925305d40d752e2eee7

--- /dev/null

+++ b/docs/v8_c_plus_plus_styleand_sops.md

@@ -0,0 +1,7 @@

+# Introduction

+In general, V8 should conform to Google's/Chrome's C++ Style Guide for new code that is written. Your V8 code should conform to them as much as possible. There will always be cases where Google/Chrome Style Guide conformity or Google/Chrome best practices are extremely cumbersome or underspecified for our use cases. We document these exceptions here.

+# Details

+Coming Soon

« docs/building_with_gyp.md ('K') | « docs/using_git.md ('k') | docs/v8_committers_responsibility.md » ('j') | no next file with comments »