Skip to content

Conversation

@Glenn
Copy link

@Glenn Glenn commented Aug 27, 2013

update latest fast_get txt into my extension

grosser and others added 30 commits May 20, 2024 20:28
Running the test suite with RUBYOPT="--enable-frozen-string-literal"
simulates Ruby's future behavior having frozen string on by default.
This fixed the error that happens with this option enabled by marking two strings which are mutated as mutable with the + operator.
run with frozen strings in ci
…nt behavior

Previously String#% was overridden on versions after Ruby 1.9 to match the 1.8 behavior where missing keys in the expanded format are ignored and not replaced. This is likely suprising behavior in modern Ruby. This removes the previous patch, but still allows overriding this behavior optionally by calling `FastGettext.allow_invalid_keys!`.
Convert String#% to Ruby 1.9+ behavior with option use maintain current behavior
a small warning, while running in `$VERBOSE` mode:
```
gems/fast_gettext-4.1.0/lib/fast_gettext/vendor/mofile.rb:182: warning: assigned but unused variable - i
```
drop unused local variable in vendor/mofile.rb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.