On Tue, Feb 6, 2018 at 5:44 PM, Jan de Mooij wrote:
> I don't think so. We could add JS_New(Latin1)String that takes Latin1Char*
> instead of char16_t* (like JS_NewUCString, it can just forward to
> js::NewString).
Thanks. I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1436065
--
Henri Si
I don't think so. We could add JS_New(Latin1)String that takes Latin1Char*
instead of char16_t* (like JS_NewUCString, it can just forward to
js::NewString).
Hope this helps,
Jan
On Tue, Feb 6, 2018 at 3:36 PM, Henri Sivonen wrote:
> Does SpiderMonkey expose a Latin1 analog of JS_NewUCString() f
Does SpiderMonkey expose a Latin1 analog of JS_NewUCString() for Gecko to call?
--
Henri Sivonen
hsivo...@hsivonen.fi
https://hsivonen.fi/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
3 matches
Mail list logo