Install and run Scarp
Choose the right package, verify its checksum, and run the executable from its extracted folder.
Installation guide ↗Scarp support
A question is
a good place to start.
Find a guide, narrow down a problem, or bring a reproducible example to the project.
Guidance targets v0.0.5-alpha.1 · Experimental prerelease
Start with the right guide
What are you
working through?
Check your version
Older executables can use different syntax. Confirm your version before following an example.
Compatibility guide ↗Understand an error
Look up an error code, read the source location, and follow the diagnostic’s repair guidance.
Diagnostic reference ↗Resolve an import
Check relative .srp paths, the trusted entry directory, public exports, and import cycles.
Source module guide ↗Explore numerical behavior
Check finite values, compatible types, vector dimensions, and the operation’s documented limits.
Numerical guide ↗Investigate a runtime limit
Inspect loop termination and numerical allocations before changing an execution budget.
Budget reference ↗हिंदी में सहायता चाहिए? हिंदी समस्या समाधान गाइड खोलें ↗
A quick first check
Confirm the version.
Then try a small example.
Run the extracted executable directly. This avoids accidentally using another Scarp installation on your PATH.
Linux / macOS
./scarp --version
./scarp run examples/hello.srpWindows PowerShell: use ./scarp.exe in place of ./scarp.
The command is not found
Run Scarp from its extracted folder with ./scarp or ./scarp.exe in PowerShell. Check the executable’s location before changing your PATH. See the installation guide.
check succeeds but prints nothing
A successful scarp check file.srp is intentionally silent. It evaluates the selected path without replaying output. Use scarp run file.srp to see the program’s output.
An example reports old or unknown syntax
Compare --version with the tutorial’s baseline. Older releases may use let or println. The current baseline uses bind and print; see compatibility.
build or compile is rejected
The published interpreter provides run, check, and tokens. Native-code compilation is future work. Review the current capabilities.
Make the next step useful
Bring the problem
to the right place.
Search existing issues first.
Include a small example others can reproduce.
Language or runtime
Scarp programs, command-line behavior, feature ideas, and interpreter bugs.
Language issue tracker ↗Documentation
Tutorial mistakes, translations, unclear explanations, and broken documentation links.
Documentation issue tracker ↗This website
Project-hub content, navigation, accessibility, and display or interaction problems.
Website issue tracker ↗What to include in a report
Prepare a guided report draft →
- Your Scarp version, operating system, and CPU architecture.
- The exact command and the smallest example that reproduces the issue.
- What you expected and the actual output or complete diagnostic.
- For a website or docs issue: the page URL and, when relevant, your browser.
GitHub issues are public. Remove credentials and private paths before posting. The contribution guide explains how to follow up with a focused change.
A little structure helps
Prepare a report for GitHub.
Choose the destination, add the details you want to share, and review your draft. You submit the issue on GitHub.
Review your draft
Project correspondence
Need to contact
the project?
For general correspondence, email scarplang@gmail.com. Public, reproducible technical questions belong in the issue trackers above.
Scarp is an early open-source project. Support is community based; no guaranteed response time or paid support plan is advertised.