[
https://issues.apache.org/jira/browse/COUCHDB-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mateusz Charytoniuk updated COUCHDB-2558:
-----------------------------------------
Description: It seems that SpiderMonkey has JS_EncodeStringToBuffer API
function that apparently does the same thing as enc_string from
src/couchdb/priv/couch_js/utf8.c . Is there a reason to use enc_string instead
of JS_EncodeStringToBuffer inside couchdb (at least in sm185.c because this API
function was added in spidermonkey 1.8.5)? (was: It seems that SpiderMonkey
has JS_EncodeStringToBuffer API function that apparently does the same thing as
enc_string from src/couchdb/priv/couch_js/utf8.c . Is there a reason to use
enc_string instead of JS_EncodeStringToBuffer inside couchdb?)
> enc_string vs JS_EncodeStringToBuffer
> -------------------------------------
>
> Key: COUCHDB-2558
> URL: https://issues.apache.org/jira/browse/COUCHDB-2558
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Reporter: Mateusz Charytoniuk
>
> It seems that SpiderMonkey has JS_EncodeStringToBuffer API function that
> apparently does the same thing as enc_string from
> src/couchdb/priv/couch_js/utf8.c . Is there a reason to use enc_string
> instead of JS_EncodeStringToBuffer inside couchdb (at least in sm185.c
> because this API function was added in spidermonkey 1.8.5)?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
