Neil Hodgson wrote:
>
>...
>
> Not making bindings explicit may mean that translators use other
> variables available at the translation point leading to unexpected failures
> when internal details are changed.
Actually, I don't think that is the case. I think that the security
implications of "_" are overstated.
name = "Paul"
country = "Canada"
password = "jfoiejw"
_('${name} was born in ${country}')
The "_" function can use a regular expression to determine that the
original code used only "${name}" and "${country}". Then it can disallow
access to ${password}
def _(origstring):
orig_substitions = get_substitutions(origstring)
translation = lookup_translation(origstring)
translation_substitions = get_substitutions(translation_substitions)
assert translation.substitutions == orig_substitutions
Paul Prescod
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4