pineforge-codegen

PineScript v6 → C++ transpiler that emits against the pineforge-engine runtime.

A pure-Python library that turns a PineScript v6 strategy into a complete C++ source file you can compile against the pineforge-engine runtime.

Measured 2026-10-05 on main engine 52292db9 with codegen-oss 48e7a13b (baseline pineforge-parity-baseline-20261005-engine-52292db9, snapshot 7161ebdc): 7,970 of 7,989 TradingView probes graded excellent and 19 strong, with 0 below strong; 17 more probes are held out as TradingView-side anomalies. A probe is a strategy exported from TradingView with its trade list and replayed trade for trade on the same bars.

Release 1.2.0 grades 7,970 excellent / 19 strong until the next release, on 7,989 probes (baseline pineforge-parity-baseline-20261005-engine-52292db9, 2026-10-05). A main scoreboard advance does not change release results.

The quantities above render from the public facts tokens. Maintain them with lab facts render --repo . --facts <local facts file or pinned raw URL>; lab facts check with the same inputs reports drift. Grades are registry-derived; the authored-script and closed-trade inventory is explicitly sourced to a historical public README for the identical population, not to registry row or slug totals.

The engine's validation scoreboard describes how a probe is graded.

It is source-available and free for personal trading — research, backtest, and trade your own account with your own capital at no cost. See License for the line between personal and commercial use.

See the changelog for the changes in each release from 1.0.0 on and the release-note policy.

Pure Python, zero runtime dependencies — transpile() and transpile_full() are the supported Python entry points.
Located diagnostics — the support checker rejects unsupported Pine with a file:line:col location before any C++ is emitted, and transpile_full() returns warnings for supported scripts with documented approximations.

Releases and this README

This README ships with each release as its package description on PyPI (pineforge-codegen); releases from 0.7.0 on are also on npm as @pineforge/codegen-pyodide. It describes 1.2.0 (2026-10-05) and what changed since 0.10.4. The PyPI release history lists every release; the changelog covers 1.0.0 on and links the notes of earlier releases. A source install reports the version in VERSION, which the release workflow sets when it tags a release.

Upgrading from 0.10.4

0.10.4 (2026-09-06) was the last 0.x release. Its README is at the v0.10.4 tag. This README marks where 0.10.4 is known to differ from 1.0.0; the changelog is the complete list. The differences a user meets first:

0.10.4's C++ derives GeneratedStrategy from BacktestEngine in <pineforge/engine.hpp>; 1.0.0's derives it from pineforge::source::PineStrategyHost. The two need different engines (see Engine pairing).
0.10.4 has no libraries= argument, no diagnostics key in transpile_full()'s result and none of the input limits.
0.10.4 recovers from some syntax errors and still returns C++; 1.0.0 raises a located CompileError instead.
Many scripts that 0.10.4 refuses transpile with 1.0.0, and some lower differently; the changelog lists them.

What this owns

This repository owns Pine → C++ translation only. It turns a Pine v6 script into a GeneratedStrategy: the indicator math plus the strategy.entry / exit / close / … calls, emitted on the engine's pineforge::source::PineStrategyHost with code that attaches the engine's Pine execution adapter.

It does not own execution semantics. Order lifecycle, bracket legs, fill-price and slippage rules, process_orders_on_close / calc_on_order_fills, margin revival and trail/stop behaviour — everything TradingView parity depends on at run time — live in the engine's source-adapter runtime (src/source/ in engine v1.2.0), which maps them onto the engine's Pine-agnostic kernel. See the engine's architecture notes.

Install

pip install pineforge-codegen

This installs the latest release. Requires Python ≥ 3.11. No runtime dependencies.

To get main, install from source (this is also the development setup):

git clone https://github.com/pineforge-4pass/pineforge-codegen-oss.git
cd pineforge-codegen-oss
pip install -e ".[dev]"

Quick start

from pineforge_codegen import transpile

pine = """
//@version=6
strategy("SMA cross", overlay=true)
fast = ta.sma(close, 10)
slow = ta.sma(close, 30)
if ta.crossover(fast, slow)
    strategy.entry("long", strategy.long)
if ta.crossunder(fast, slow)
    strategy.close("long")
"""

cpp = transpile(pine)
print(cpp)          # complete C++ source string

The output #includes <pineforge/source/pine_strategy_host.hpp>, <pineforge/ta.hpp>, …; its GeneratedStrategy derives from pineforge::source::PineStrategyHost and compiles into a .so exposing the engine's documented C-ABI. 0.10.4's output includes <pineforge/engine.hpp> and derives from BacktestEngine. Compile & run against the engine builds and runs this strategy.

Usage

The `transpile()` function

transpile(
    pine_source: str,
    *,
    check_support: bool = True,   # run the support checker before codegen
    filename: str = "<input>",    # name used in error locations
    libraries: Mapping[str, str] | None = None,   # imported Pine libraries (new in 1.0.0)
) -> str

Returns the generated C++ source as a string. Raises pineforge_codegen.errors.CompileError on a rejected construct and, since 1.0.0, on a syntax error or an input limit (0.10.4 recovers from some syntax errors and has no input limits). It does not return nonfatal warnings; use transpile_full() to inspect them.

libraries is new in 1.0.0. It maps an import path to the library's source ({"user/name/version": source_text}), and each import the script uses is inlined from it. With libraries=None (the default) the sources are read through the script's own requests manifest when the environment names one ($PINEFORGE_PINE_LIBRARIES with $PINEFORGE_REQUESTS_ROOT); otherwise an import is refused by name, as in 0.10.4. Since 1.0.0, an import whose alias is ta, math or str and that names only that namespace's built-ins needs no source.

The `transpile_full()` function

transpile_full(
    pine_source: str,
    *,
    check_support: bool = True,
    filename: str = "<input>",
    libraries: Mapping[str, str] | None = None,   # new in 1.0.0
) -> dict

It returns {"cpp": str, "inputs": list[dict], "strategyParams": dict, "diagnostics": list[Diagnostic], "requests": list[dict]} on success (0.10.4 returns the first three keys; requests is new in 1.1.0). inputs is the input manifest; its title is the actual override key, and an input.symbol entry also has "kind": "symbol" (since 1.1.0). diagnostics contains nonfatal warnings. requests lists the other symbols' feeds the script reads (see List the other symbols a script requests). A rejected script raises CompileError with its diagnostics. The Pyodide package ships gate/glue.py's transpile_json(source) -> str, whose JSON success and error envelopes carry the same manifest and, since 1.0.0, the same warnings; since 1.1.0 the success envelope also carries requests. See the 1.0 public contract for the exact fields, severity values, and input key rules. There is no installed CLI or exit-code contract.

Diagnostic codes

Every diagnostic carries a stable code and named args (since 1.2.0): PF-E1203 for an error, PF-W0412 for a warning, and the data its English message and hint were built from — identifiers, types, keywords and numbers, raw.

from pineforge_codegen import diagnostics_catalog, transpile_full

for d in transpile_full(source)["diagnostics"]:
    print(d.code, d.args, d.message)
# PF-W1067 {'name': 'bar_index'} bar_index diverges from TradingView semantics in PineForge.

entry = diagnostics_catalog()["codes"]["PF-W1067"]
# {'severity': 'warning', 'area': 'support',
#  'message': '{name} diverges from TradingView semantics in PineForge.',
#  'hint': '...', 'explanation': '...', 'args': {'name': {'kind': 'identifier'}}}

The catalog (pineforge_codegen/diagnostics_catalog.json, also attached to each GitHub release) gives each code its severity, English ICU MessageFormat templates and a one-line explanation; rendering the templates with args gives the message and hint byte for byte, so an application can translate a diagnostic by its code. Codes are never reused. See Diagnostic codes.

List the other symbols a script requests

A run reads another symbol's bars only from the feed it is given for that symbol string and timeframe, matched byte for byte. transpile_full()'s requests (new in 1.1.0) names those feeds before the run, one entry per request site:

from pineforge_codegen import transpile_full

full = transpile_full(open("my_strategy.pine").read())
for request in full["requests"]:
    print(request)
# {'line': 7, 'fn': 'request.security',
#  'symbol': {'kind': 'input', 'title': 'Other symbol', 'default': 'BINANCE:ETHUSDT'},
#  'timeframe': {'kind': 'chart'},
#  'lookahead': False, 'gaps': False, 'ignore_invalid_symbol': False}

The symbol is a literal (its value), an input (its override key title and its default: the run keys the feed on the override, else the default), computed (its expr, the value at the inputs' defaults when it can be computed, and the inputs it reads) or unresolvable (a request PineForge cannot key before the first bar: the run stops where its value is read). The timeframe is a literal in the engine's spelling (whole minutes such as "240", <n>D|W|M|S such as "1D", Pine's bare "D" as "1D"), the chart's, an input or computed (an empty value is the chart's). A request whose value reaches only plots and alerts is lowered to na and reads no feed, so it is not listed. The public contract gives every field.

Transpile a file to a `.cpp`

from pathlib import Path
from pineforge_codegen import transpile

pine = Path("strategy.pine")
cpp = transpile(pine.read_text(), filename=pine.name)   # filename → better errors
Path("strategy.generated.cpp").write_text(cpp)

Handle unsupported features

The support checker raises a CompileError with the exact source location instead of emitting broken C++:

from pineforge_codegen import transpile
from pineforge_codegen.errors import CompileError

try:
    transpile('//@version=6\nindicator("x")\n')
except CompileError as e:
    print(e)
    # <input>:2:1: indicator() declarations are not supported; PineForge runs strategies only.

try:
    transpile('//@version=6\nstrategy("x")\n'
              'x = request.seed("seed_crypto_santiment", "BTC_SENTIMENT_POSITIVE_TOTAL", close)\n')
except CompileError as e:
    print(e)
    # <input>:3:17: request.seed(...) is not supported.

Pass filename= so the location points back at the user's file:

transpile(src, filename="my_strategy.pine")
# raises e.g.  my_strategy.pine:12:5: ...

Not every request for outside data is refused. A request.financial() whose value reaches only plots, alerts, tables or logs transpiles with a warning and reads na; 0.10.4 refuses it. The changelog lists what 1.0.0 reads, warns about or refuses for such requests.

Skip the support checker

check_support=False on either Python function is experimental. It bypasses the gate and can produce C++ the engine will not accept or execute faithfully:

from pathlib import Path
from pineforge_codegen import transpile

src = Path("strategy.pine").read_text()
cpp = transpile(src, check_support=False)

Trace intermediate expressions (`@pf-trace`)

A // @pf-trace name=expr comment, alone on its line, makes the compiled strategy record name's value on every bar when tracing is enabled with the engine's strategy_set_trace_enabled(); the values come back in the report's trace array (pf_report_t::trace). That is useful for debugging parity against TradingView:

from pineforge_codegen import transpile

pine = """
//@version=6
strategy("traced")
// @pf-trace rsi=r
r = ta.rsi(close, 14)
e = ta.ema(close, 20)
if close > e
    strategy.entry("L", strategy.long)
"""
cpp = transpile(pine)   # emitted on_bar tail records `r` each bar

Trace a script variable or an expression over script variables and bar fields, such as // @pf-trace gap=close - e or // @pf-trace body=math.abs(close - open). A ta.* call written in the pragma itself is not computed: // @pf-trace rsi=ta.rsi(close, 14) records na on every bar, and its C++ carries an /* unsupported: ta.rsi */ marker. 0.10.4, 1.0.0, 1.0.1, 1.1.0 and 1.2.0 all behave this way.

Advanced: run the pipeline stages directly

Drive the main stages yourself to inspect tokens, the AST, or the analyzer context. These classes are outside the 1.0 public contract:

from pineforge_codegen import (
    Lexer, Parser, Analyzer, CodeGen,
    extract_pf_trace_pragmas, check_support_or_raise,
)

src = open("strategy.pine").read()
pragmas = extract_pf_trace_pragmas(src)
tokens  = Lexer(src, filename="strategy.pine").tokenize()
ast     = Parser(tokens, source=src, filename="strategy.pine").parse()
check_support_or_raise(ast, filename="strategy.pine")
ctx     = Analyzer(ast, filename="strategy.pine").analyze()
ctx.pf_trace_pragmas = pragmas
cpp     = CodeGen(ctx).generate()

This skips the library inlining, the AST rewrites and the reruns that transpile() also performs (see How it works). Its C++ equals transpile()'s only for scripts those passes leave unchanged, such as the quick-start strategy.

Limits

These limits are new in 1.0.0; 0.10.4 has none of them. They turn a crash or a hang on untrusted source into a CompileError with a Pine file:line:col location. Where TradingView documents a limit, PineForge's is at least as large. Exceeding one does not return partial C++, and check_support=False does not bypass them.

Limit	Maximum	TradingView's documented limit	Largest in the 325 public corpus sources and 277 gate fixtures
Source size	5,242,880 characters (5 MiB)	Compilation request of at most 5MB	9,869 characters
Nesting depth	512 levels	None	10 levels
Transpilation time	120 seconds	Two-minute compilation limit	0.05 seconds

The last column was measured on 2026-09-29 with 70c2b4a (the same code as 1.0.0) on CPython 3.14 on an Apple M4 Max, over the engine corpus that engine 35db01c8 pins (as v1.0.0, v1.0.1, v1.1.0 and v1.2.0 do) and this repository's tests/gate-corpus. On 2026-10-05, on CPython 3.14 on an Apple M4 Max, 1.2.0 transpiled each of those sources in under 0.1 seconds.

Nesting counts brackets, indented blocks, prefix operators, ?: and else if chains, and the depth of the parsed syntax tree, in which an operator chain such as a + b + c takes one level per operator. It stops well before Pyodide's stack does, at about 2,000 levels. There is no statement-count or statement-size limit: TradingView measures a script in compiled tokens, not source lines. transpile() raises Python's recursion limit to 20,480 frames when it is lower, and never lowers it. The elapsed-time guard checks the lexer, parser, analyzer and code generator cooperatively. Numeric literals outside the generated C++ range also raise a located error.

How it works

transpile() runs these passes, in order:

pine source
  │
  ├─ 1. extract_pf_trace_pragmas   // @pf-trace comments pulled out first
  ├─ 2. Lexer → Parser             token stream → Pine v6 AST
  ├─ 3. library inlining           imported Pine libraries inlined into the AST
  ├─ 4. support_checker            reject anything the engine can't run faithfully
  ├─ 5. AST rewrites               requests with no data, request.security contexts,
  │                                bounded TA lengths, builtin keyword arguments
  ├─ 6. Analyzer                   type inference, scope resolution, TA bookkeeping
  └─ 7. CodeGen                    → C++ source string

The passes run again, from pass 1, when the generated C++ needs a renamed block-local declaration or a per-call-site clone of a function that reads session.<flag>[k]; _generate in pineforge_codegen/__init__.py holds the loop. 0.10.4 runs passes 1, 2, 4, 6 and 7 once, with only the bounded TA length rewrite of pass 5.

The emitted GeneratedStrategy does not execute orders itself: its strategy.* calls go to the engine's Pine execution adapter, which it attaches in its constructor.

Engine pairing

Generated C++ compiles only against the engine it was generated for:

Codegen	Engine	Status
0.10.4 (PyPI, 2026-09-06)	`v0.13.1`	The last 0.x pair, which the `pineforge-release` image `0.1.25` ships. Its C++ does not compile against engine `v1.0.0`.
1.0.0 (PyPI, 2026-09-30)	`v1.0.0`	The pair the `pineforge-release` image `1.0.0` ships. Its C++ needs `pineforge/source/pine_strategy_host.hpp`, which engine `v0.13.1` does not have.
1.0.1 (PyPI, 2026-10-02)	`v1.0.1`	The pair the `pineforge-release` image `1.0.1` ships. Engine `v1.0.1` changes only documentation since `v1.0.0`; regenerate and relink all the same.
1.1.0 (PyPI, 2026-10-04)	`v1.1.0`	The pair the `pineforge-release` image `1.1.0` ships. Its C++ defines the checked settings functions that engine `v1.1.0` adds to `<pineforge/pineforge.h>`; regenerate and relink.
1.2.0 (PyPI, 2026-10-05)	`v1.2.0`	The pair the `pineforge-release` image `1.2.0` ships. Its C++ defines the compiled execution capability functions that engine `v1.2.0` adds to `<pineforge/pineforge.h>`; regenerate and relink.
Later `X.Y.Z` releases	`vX.Y.Z` of the same version	See below.

On the 0.x line the engine and codegen versions are independent, and the pineforge-release image records which pair it ships. From 1.0.0 on, a released codegen X.Y.Z is supported only with engine tag vX.Y.Z, using that release's generated headers and static library. Prereleases match exactly: codegen 1.0.0-rc.1 requires engine v1.0.0-rc.1. On every pair change, regenerate the strategy C++ from Pine and relink it against that engine release's headers and libpineforge.a. PF_ABI_VERSION equality alone is insufficient; it does not guarantee the C++ source layout or behavior. Development branches can test paired in-progress commits, but they are not supported cross-version release pairs. See CONTRIBUTING.md for the setup and checks.

Compile & run against the engine

The emitted C++ targets the C-ABI in <pineforge/pineforge.h>. The engine's tutorial/ builds libpineforge.a and a strategy .so and runs it on 672 frozen BTCUSDT 15m bars. To run your transpiled strategy there, save the quick-start Pine as strategy.pine, write strategy.generated.cpp with the file example above, then from the same directory:

# 1.2.0 pairs with engine v1.2.0. For 0.10.4 use --branch v0.13.1.
git clone --branch v1.2.0 https://github.com/pineforge-4pass/pineforge-engine.git
cd pineforge-engine
cp ../strategy.generated.cpp tutorial/macd/generated.cpp   # the tutorial's strategy slot
bash tutorial/run.sh    # needs cmake, a C++17 compiler and python3

run.sh configures CMake once, builds libpineforge.a and tutorial/macd/strategy.so, and runs tutorial/run.py, which loads the .so, feeds it the bars and reads back the closed trades. For the quick-start SMA cross, 1.2.0 with engine v1.2.0 prints:

MACD(12,26,9) on BTCUSDT 15m — 672 bars, 2026-04-29 18:15 → 2026-05-06 18:00 UTC
  trades:    9  (6W / 3L, 66.7% win)
  net pnl:   +738.20
  best/worst:+679.22 / -335.02
  max dd:    -788.79
  elapsed:   1.0 ms

The MACD(12,26,9) label on the first line is fixed text in run.py, whatever strategy the .so holds, and elapsed varies by machine. 0.10.4 with engine v0.13.1 books 13 trades on the same bars. The difference is order sizing: 1.0.0 gives an omitted initial_capital, default_qty_type and default_qty_value TradingView's Pine v6 defaults (100,000, strategy.percent_of_equity, 100), where 0.10.4 leaves the engine's own (1,000,000 and 1 contract). Declaring those in strategy() books the same 13 trades on 1.2.0.

Since 1.0.0, generated strategies reset persistent Pine state before each new batch or stream warmup through the engine's script-run preparation hook. Input settings survive a new run, and ticks within one stream preserve accumulated state. Regenerate the strategy C++ and rebuild compiled modules with matching engine headers and library to use this lifecycle; replacing only the runtime archive does not retrofit already compiled modules.

Since 1.0.0, generated constructors do not configure order behavior from the presence of strategy.close or strategy.close_all in the source. Older C++ (0.10.4's included) assigns script_has_strategy_close_, which engine v1.0.0 has removed; regenerate it before compiling there. Reachable close commands keep their ordinary runtime lowering.

Prefer no local build? pineforge.dev runs a free hosted MCP server, with a weekly backtest quota, whose backtest_pine tool transpiles and backtests a strategy for an AI agent. The pineforge-backtest-mcp Docker image is a local MCP server with transpile_pine and backtest_pine tools that runs on your machine. Both are built on the pineforge-release image, which ships a released codegen and engine pair; their engine_info tool reports the image's version.

Running tests

The full release check needs matching engine headers, a generated pineforge/version.h, Eigen, the built runtime, and the public engine corpus. Run python -m pytest -ra and then python -m pytest -ra tests/test_compile_corpus.py with those paths set; check the skip reasons so compiler and runtime coverage actually ran. The full Pyodide parity gate and npm audit are also required. The exact setup and commands are in CONTRIBUTING.md; use python -m pytest --collect-only -q for the current collection count.

License

Source-available under the PineForge Source License 1.1; the LICENSE file is the controlling text. The licensor is pineforge, LLC.

Free for noncommercial use: any noncommercial purpose, and use by a charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization or government institution for its teaching, research and other operations.
Free for Personal Trading: a natural person may research, develop or backtest strategies and execute trades for their own account with their own capital. Their own account includes joint and household accounts (spouse or domestic partner, dependants), retirement and other tax-advantaged accounts and a revocable trust for their benefit; their own capital includes margin and other ordinary borrowing from a broker or lender. A company's or fund's account is not a personal account, even if the person wholly owns the company.
Investment management is never free, except Personal Trading: managing, advising on or trading investment capital, or researching strategies for it, whether the capital is a friend's, clients' or investors', an endowment, a pension fund, a public fund or a foundation's treasury, is Commercial Use for every individual and every organization, noncommercial organizations included.
Commercial Use needs a commercial license: besides investment management, any other use that is not free, such as use by, for or on behalf of a company, fund, partnership or other organization (including an individual's work for one); embedding the software or its output in, or distributing either bundled with, a product or service made available to others; or operating a hosted, software-as-a-service or other public-facing service through which others run the software or receive its output.

This is source-available, not OSI open source.

Buying a commercial license

Commercial licenses are annual: Solo for one person, Team for an organization's own use, Fund for managers of others' capital and for institutional investment capital such as endowments and pension or public funds (by assets under management), and OEM / Embedded for products and hosted services. Email enterprise@pineforge.dev with questions or for a quote. The commercial-license store (coming soon) will take orders online.

Explicit Pine execution attachment

This section describes 1.2.0 and engine v1.2.0. The Pine execution adapter is the engine's full Pine execution runtime (PineExecutionAdapter and PineStrategyHost in the engine's src/source/): order lifecycle, bracket legs, fill-price and slippage rules, POOC / calc_on_order_fills, margin revival, trail/stop semantics, the intraday caps and the retained-parent priority rule. Codegen's job is to emit the strategy that attaches it and the strategy.* calls it executes, against a matching engine ABI.

Generated constructors configure their PineStrategyConfig before host metadata and select attach_pine_execution_adapter() when PINEFORGE_HAS_EXPLICIT_PINE_EXECUTION_ADAPTER_V1 is available, with a guarded enable_pine_intraday_cap() fallback for PINEFORGE_HAS_EXPLICIT_PINE_CAP_V1 alone. Every engine header the generated C++ can compile against (those with pineforge/source/pine_strategy_host.hpp) defines both macros, so the adapter branch is the one compiled; see docs/pine-cap-activation.md. Risk statements remain in source execution order. This bridge requires matching engine headers and runtime; it is not cross-version C++ binary compatibility.

Regenerate old generated C++ before using a new engine for Pine execution. C++ generated before the source-layer cut (#129), 0.10.4's included, derives from BacktestEngine and does not compile against engine v1.2.0; old cap-only C++ does not attach the priority rule, and metadata cannot silently restore it. Rebuild all modules against the new matching C++ layout (engine_script_run_v19 in engine v1.2.0); old fingerprint versions are not comparable. The extraction preserves Pine policy under explicit attachment; it does not implement the generic native child-activation scheduler or prove campaign neutrality. Compile-only corpus checks do not run Pine backtests.

Name		Name	Last commit message	Last commit date
.claude		.claude
.github		.github
docs		docs
gate		gate
npm		npm
pineforge_codegen		pineforge_codegen
scripts		scripts
tests		tests
.gitignore		.gitignore
AGENTS.md		AGENTS.md
CHANGELOG.md		CHANGELOG.md
CLAUDE.md		CLAUDE.md
CONTRIBUTING.md		CONTRIBUTING.md
LEGAL.md		LEGAL.md
LICENSE		LICENSE
PYODIDE_TARGET		PYODIDE_TARGET
README.md		README.md
VERSION		VERSION
package-lock.json		package-lock.json
package.json		package.json
pyproject.toml		pyproject.toml

Navigation Menu

Repository files navigation

pineforge-codegen

Releases and this README

Upgrading from 0.10.4

What this owns

Install

Quick start

Usage

The `transpile()` function

The `transpile_full()` function

Diagnostic codes

List the other symbols a script requests

Transpile a file to a `.cpp`

Handle unsupported features

Skip the support checker

Trace intermediate expressions (`@pf-trace`)

Advanced: run the pipeline stages directly

Limits

How it works

Engine pairing

Compile & run against the engine

Running tests

License

Buying a commercial license

Explicit Pine execution attachment

About

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

pineforge-codegen

Releases and this README

Upgrading from 0.10.4

What this owns

Install

Quick start

Usage

The transpile() function

The transpile_full() function

Diagnostic codes

List the other symbols a script requests

Transpile a file to a .cpp

Handle unsupported features

Skip the support checker

Trace intermediate expressions (@pf-trace)

Advanced: run the pipeline stages directly

Limits

How it works

Engine pairing

Compile & run against the engine

Running tests

License

Buying a commercial license

Explicit Pine execution attachment

About

Topics

Resources

Contributing

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

The `transpile()` function

The `transpile_full()` function

Transpile a file to a `.cpp`

Trace intermediate expressions (`@pf-trace`)