So far none is planned, because automated imports of Delphi libraries proved to be of limited value.
DWScript is a sand-boxed script that aims to allow the host application to survive any bad behaviors or bugs in scripts, and the overwhelming majority of Delphi code out there (RTL, VCL & FMX included) won't allow that without a (usually major) layer of manually-written sanity checks and fail-safes.
For instance, take something as simple as a TCollection, if you were to expose it directly to scripts, then the following script would result in memory corruption of the host application:
This and similar simple occurrences mean that with automated imports, it is impossible to safely debug scripts f.i., let alone run them in a sand-boxed fashion.
So far none is planned, because automated imports of Delphi libraries proved to be of limited value.
ReplyDeleteDWScript is a sand-boxed script that aims to allow the host application to survive any bad behaviors or bugs in scripts, and the overwhelming majority of Delphi code out there (RTL, VCL & FMX included) won't allow that without a (usually major) layer of manually-written sanity checks and fail-safes.
For instance, take something as simple as a TCollection, if you were to expose it directly to scripts, then the following script would result in memory corruption of the host application:
item := Collection.Add;
Collection.Delete(Collection.Count-1);
item.Caption := 'kaboom';
This and similar simple occurrences mean that with automated imports, it is impossible to safely debug scripts f.i., let alone run them in a sand-boxed fashion.