Skip to content

Commit 09810ab

Browse files
authored
Update README.md
1 parent c45cc36 commit 09810ab

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

coding_conventions/README.md

+12-12
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,11 @@ The goal of these Coding Conventions is to present a set of best practices and s
1515

1616
### Table of Contents
1717

18-
- [Script Structure](#script-structure)
19-
- [Naming Conventions](#naming-conventions)
20-
- [Spacing](#spacing)
21-
- [Line Wrapping](#line-wrapping)
22-
- [Example Scripts](#example-scripts)
18+
- [Script Structure](#script-structure)
19+
- [Naming Conventions](#naming-conventions)
20+
- [Spacing](#spacing)
21+
- [Line Wrapping](#line-wrapping)
22+
- [Example Scripts](#example-scripts)
2323

2424

2525
<br>
@@ -36,13 +36,13 @@ The Pine compiler is not very strict on exact positioning of specific statements
3636

3737
1. The next lines should contain the following sections, properly identified if they are long:
3838

39-
- Constant initializations
40-
- Inputs
41-
- Functions
42-
- Calculations
43-
- Strategy calls (for strategies)
44-
- Plots
45-
- Alerts
39+
- Constant initializations
40+
- Inputs
41+
- Functions
42+
- Calculations
43+
- Strategy calls (for strategies)
44+
- Plots
45+
- Alerts
4646

4747
1. The following lines can contain **variable initializations** and **function definitions** in any order required. Note that all Pine functions must be defined in the script's global scope, as nested function definitions are not allowed. Concerning variable initializations, some scripts lend themselves to mass initializations and others will be more readable with an *initialize as you need* style that places initializations with the code segments where the variables are used. It's up to each coder to adopt the most useful style. Local block variables must be declared in the local block where they will be used.
4848

0 commit comments

Comments
 (0)