-
-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
regression with closures in maps (since 3.4.0) #1550
Comments
Reviewing the details in this issue again, I notice the URL to the HoF article that Peter referenced in his exist-open post unfortunately isn’t working: http://atomic.exist-db.org/blogs/eXist/HoF...
|
The URL http://atomic.exist-db.org/blogs/eXist/HoF does work for me … maybe just a temporary server error? |
There were temporary hiccups with some pages on the server yesterday, which I fixed in the meantime. It's best to point to http://exist-db.org/exist/apps/wiki/blogs/eXist/HoF though since http://atomic.exist-db.org is an old redirect. |
While I congratulate to the 4.0 release I tentatively want to remind you of this issue. It's something that keeps me from upgrading so I'm currently stuck with version 3.3.0. Many thanks in advance! |
I had a look into this issue before 4.0 and I see where the problem is, but it's not straightforward to fix without potentially causing other regressions, so I did not want to risk it for the release. |
Thanks for the reply! I was just trying to make sure it wont be forgotten ;) |
Help! This is really an issue for me that prevents me from upgrading to a recent eXist version. Is a fix anywhere on the roadmap or do I have to refactor my code? |
Assigning high prio for myself. |
Sorry for bothering, but is there any chance this will be tackled in the near future? |
not directly related, but because namespace prefixes can appear in maps, the preferred and specs compliant map syntax is return
map {
'test1': $func,
'test2': $func(),
'test3': function() {
$param
}
}
only one ws after |
@peterstadler I think you will have to ask @wolfgangmm |
@duncdrum shall I create a PR for the tests? |
…iables were not analyzed properly. This affects XQ Suite tests, reporting wrong failures, but also eXist-db#1550.
…iables were not analyzed properly. This affects XQ Suite tests, reporting wrong failures, but also eXist-db#1550.
…iables were not analyzed properly. This affects XQ Suite tests, reporting wrong failures, but also eXist-db#1550.
…iables were not analyzed properly. This affects XQ Suite tests, reporting wrong failures, but also eXist-db#1550.
…iables were not analyzed properly. This affects XQ Suite tests, reporting wrong failures, but also eXist-db#1550.
…iables were not analyzed properly. This affects XQ Suite tests, reporting wrong failures, but also eXist-db#1550.
…iables were not analyzed properly. This affects XQ Suite tests, reporting wrong failures, but also eXist-db#1550.
…iables were not analyzed properly. This affects XQ Suite tests, reporting wrong failures, but also eXist-db#1550.
…iables were not analyzed properly. This affects XQ Suite tests, reporting wrong failures, but also eXist-db#1550.
What is the problem
Starting with eXist version 3.4.0 inline functions within maps will not inherit variables declared outside its function body. The problem has been discussed on eXist-open and was confirmed by @joewiz by testing against Saxon and BaseX.
What did you expect
I expected all three tests to pass without errors (as they do in eXist version 3.3.0).
Describe how to reproduce or add a test
Context information
The text was updated successfully, but these errors were encountered: