Safe mode: Difference between revisions
Added Wren blurb.
Thundergnat (talk | contribs) (→{{header|Raku}}: Fix up internal links and references) |
(Added Wren blurb.) |
||
Line 242:
Actually, with a high-level programming language as Scala, it's a bad idea to flag or unflag for a "Safe mode"..
This should be a task for the target system.
=={{header|Wren}}==
Wren code is considered to be 'safe' in itself. Method/function calls are dynamically checked and generate runtime errors which can be caught and handled. A fiber's stack grows if it gets close to overflowing. There is no support for pointers nor reflection and memory is managed automatically by the runtime.
However, when Wren is embedded in a host application, one needs to deal with the embedding API (or a wrapper thereof) to pass data between Wren and the host. The embedding API is written in C and, as such, is intrinsically unsafe. It is generally up to the programmer to ensure that API functions are passed the correct number of arguments and those arguments are of the correct types.
=={{header|zkl}}==
| |||