Minor fixups

gh-pages
Hauke D 7 years ago
parent d8f1487ec4
commit ebe314cfc1

@ -119,7 +119,7 @@ for the current details.
bitcode, which the Emscripten compiler will then compile to JavaScript/WebAssembly. bitcode, which the Emscripten compiler will then compile to JavaScript/WebAssembly.
Because some steps in the build process require a working `perl` binary, Because some steps in the build process require a working `perl` binary,
Emscripten's compiler is used together with a supporting JavaScript file to Emscripten's compiler is used together with a supporting JavaScript file to
generate JavaScript code that can be run with `node.js` (called `nodeperl_dev.js`). generate JavaScript/WebAssembly code that can be run with `node.js` (called `nodeperl_dev.js`).
8. Run the equivalent of `make install`, which copies all the Perl modules 8. Run the equivalent of `make install`, which copies all the Perl modules
etc. into the target directory that will become part of the Emscripten etc. into the target directory that will become part of the Emscripten
@ -130,7 +130,8 @@ for the current details.
9. The Emscripten compiler is used to take the previously compiled `perl.bc` 9. The Emscripten compiler is used to take the previously compiled `perl.bc`
and build the final output, `emperl.js` along with the corresponding and build the final output, `emperl.js` along with the corresponding
`.wasm` and `.data` file. `.wasm` and `.data` file. This step also includes the packaging of the
virtual filesystem.
`build.pl` provides various command-line options that allow you to control `build.pl` provides various command-line options that allow you to control
parts of the build process. See `build.pl --help` for details. parts of the build process. See `build.pl --help` for details.

@ -379,9 +379,9 @@ Arguments from Perl to JavaScript function or method calls are mapped as follows
### Mappings from Perl to JavaScript ### Mappings from Perl to JavaScript
Unlike the JavaScript to Perl mappings, values are generally *copied* from Unlike the JavaScript to Perl mappings, values are (currently) generally *copied* from
Perl to JavaScript, instead of being *referenced*. Perl to JavaScript, instead of being *referenced*.
The exceptions are Perl `subs`s and `WebPerl::JSObject`s. The exceptions are Perl `sub`s and `WebPerl::JSObject`s.
- Perl arrayrefs become JavaScript arrays - Perl arrayrefs become JavaScript arrays
- Perl hashrefs become JavaScript objects - Perl hashrefs become JavaScript objects
@ -393,7 +393,8 @@ The exceptions are Perl `subs`s and `WebPerl::JSObject`s.
(with its `allow_nonref` option enabled). This means that the choice (with its `allow_nonref` option enabled). This means that the choice
for whether to encode a Perl scalar as a JavaScript number or string is for whether to encode a Perl scalar as a JavaScript number or string is
left up to the module, and is subject to the usual ambiguities when left up to the module, and is subject to the usual ambiguities when
serializing Perl scalars. serializing Perl scalars. See
[the `Cpanel::JSON::XS` documentation](https://metacpan.org/pod/Cpanel::JSON::XS).
- Other references, including objects, are currently not supported. - Other references, including objects, are currently not supported.

Loading…
Cancel
Save