Add C++ implementation overview documentation#139
Add C++ implementation overview documentation#139rabail-aamir wants to merge 2 commits intothoth-tech:mainfrom
Conversation
stelaukin
left a comment
There was a problem hiding this comment.
I've left some suggestions about the phrasing of a few things and there are a couple of minor spelling and grammar issues.
| In a Web Worker, the actual compilation process is carried out using: | ||
|
|
||
| - **clang++.wasm**: Compiles C++ source into object files | ||
| - **wasm-ld.wasm**: Links object files into a final |
There was a problem hiding this comment.
This sentence seems incomplete. It looks like it was intended to describe the final WebAssembly output. Consider completing the sentence for clarity.
| ## Relationship with WebAssembly (WASM) | ||
|
|
||
| SplashKit Online can securely run C++ code within the browser thanks to WebAssembly. | ||
| The browser's runtime interprets WASM, which is created by the compiler from C++. |
There was a problem hiding this comment.
This sentence is understandable, but the term “interprets” may be slightly misleading. Browsers typically execute or compile WebAssembly rather than interpret it. Consider rephrasing to something like “The browser executes the compiled WebAssembly (WASM) generated from C++ code” for better technical accuracy.
|
Reviewed the PR and went through the documentation in detail. The content is well-structured and provides a clear overview of how C++ is implemented and executed in SplashKit Online. It should be helpful for new contributors to understand the overall flow. I’ve left a few minor comments regarding small typos, wording improvements, and an incomplete sentence. These are minor and do not block approval. |
Description
This document provides an overview of how C++ support is implemented in Splashkit Online, including:
It will help new contributors understand structured and flow of C++ backend and supports future improvement tasks.
Fixes # (issue)
Type of change
How Has This Been Tested?
This change affects documentation only.
No code functionality was modified.
Testing Checklist
Checklist