4 ms·
> you can solve it by blindly calling #to_i on your inputs "You can solve it by blindly calling #h on your outputs" Ouch. We know that scheme doesn't work too
by zwp 16y ago
> you can solve it by blindly calling #to_i on your inputs
"You can solve it by blindly calling #h on your outputs"
Ouch. We know that scheme doesn't work too well: it's why we had #h and we now have #html_safe...
- tptacek 16y agoNot comparable. h() was a one-sized-fits-all problem to quoting things that could occur anywhere in an HTML DOM. #to_i assures that a bit of syntax that can only ever accept integers is in fact given a real integer. In case we're misunderstanding each other, I'm also saying that the framework should be doing that, not the caller (as was the case with h()).
- zwp 16y agoThanks, yes misunderstanding: agree should be a framework protection not something developer should be sprinkling over code.