Skip to content

[ExpressionLanguage] Fixed #9606: leading spaces in expressions lead to 'Uninitialized string offset: X' warnings #9615

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

Closed
wants to merge 1 commit into from

Conversation

rolebi
Copy link

@rolebi rolebi commented Nov 26, 2013

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #9606
License MIT
Doc PR

Bug fix for #9606

…to 'Uninitialized string offset: X' warnings
@fabpot
Copy link
Member

fabpot commented Nov 26, 2013

Thanks for working on this. I've done a slightly different fix in #9621 to avoid loosing the correct cursor on such expressions.

@fabpot fabpot closed this Nov 26, 2013
fabpot added a commit that referenced this pull request Nov 28, 2013
…aces (fabpot)

This PR was submitted for the master branch but it was merged into the 2.4 branch instead (closes #9621).

Discussion
----------

[ExpressionLanguage] fixed lexing expression ending with spaces

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #9606, #9615
| License       | MIT
| Doc PR        |

Alternative fix for #9615

Commits
-------

d8f61c4 [ExpressionLanguage] fixed lexing expression ending with spaces
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants