[ 
https://issues.apache.org/jira/browse/COUCHDB-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121748#comment-13121748
 ] 

Paul Joseph Davis commented on COUCHDB-1302:
--------------------------------------------

>From Benoit on the ML:

> if we do that it would imply the release of a major version since the change
> is major. I'm +1 to introduce correct behaviour in trunk rather than trying
> to hack arouind our own insanity.

I think its a good idea to revert this on 1.1.x as it could break user code for 
no good reason. Though 1.1.x will have the ability to use newer SpiderMonkey's, 
they'll have to deal with upgrading their JS code.

What we do about 1.2.x and trunk I'm less certain. On the one hand, we could 
save some people some effort. On the other hand, we'd also be breaking things 
for people that use helper functions that haven't upgraded to 1.8.5 or w/e 
version of SM introduces this.

Bottom line is that there's no good answer other than making sure we note it in 
our NEWS files, and on the website and also try and document it in error 
messages.

Quite an unfortunate situation that I see no good answer to.
                
> Fix couchjs
> -----------
>
>                 Key: COUCHDB-1302
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1302
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: JavaScript View Server
>    Affects Versions: 1.1.1, 1.2, 1.3
>            Reporter: Paul Joseph Davis
>            Priority: Blocker
>
> Figure out why some spidermonkeys have an error when doing: 
> eval("function(){}")

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to