From 0de1fc3e5b08da73a0655219895d7c311610cbce Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A9mi=20Verschelde?= Date: Wed, 25 May 2022 12:35:00 +0200 Subject: [PATCH] Fix outdated comment about GDNative on HTML5 (cherry picked from commit 790c6ca5324511f678294ae3c04a142f9f6cb8cf) --- tutorials/scripting/gdnative/what_is_gdnative.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/tutorials/scripting/gdnative/what_is_gdnative.rst b/tutorials/scripting/gdnative/what_is_gdnative.rst index 829500ff8..a062ac6e9 100644 --- a/tutorials/scripting/gdnative/what_is_gdnative.rst +++ b/tutorials/scripting/gdnative/what_is_gdnative.rst @@ -54,8 +54,9 @@ GDNative isn't enough: limited to what the scripting API exposes. - You can use C++ modules to provide additional features in a project without carrying native library files around. This extends to exported projects. -- C++ modules are supported on all platforms. In contrast, GDNative isn't - supported on HTML5 and the Universal Windows Platform (UWP) yet. +- C++ modules are supported on all platforms. In contrast, GDNative has only + limited support on HTML5 (cannot be used together with multi-threading), and + is not supported on Universal Windows Platform (UWP). - C++ modules can be faster than GDNative, especially when the code requires a lot of communication through the scripting API.