Closed frobinsonj closed 3 years ago
there is one more place to use this technique (but you'll need the condition you had before):
https://github.com/aemkei/jsfuck/blob/effccc419c274f49613580357e4898bf17327e0f/jsfuck.js#L265-L274
Thanks, I've borrowed your stuff into my PR #88
there is one more place to use this technique (but you'll need the condition you had before):
https://github.com/aemkei/jsfuck/blob/effccc419c274f49613580357e4898bf17327e0f/jsfuck.js#L265-L274
I saw that but to be honest, it was late last night and I was struggling to understand the order that everything was being called haha
Is that not just a fallback for any characters that can't already be found? I believe that all supported characters are included within MAPPING
so it would have no affect here?
Is that not just a fallback for any characters that can't already be found?
Yes
I believe that all supported characters are included within MAPPING so it would have no affect here?
In MAPPING
are only characters up to ASCII code 127. So this code block would work for characters 128-255. Not sure how much it is helpful. I think only character which can benefit from it is ß
Is that not just a fallback for any characters that can't already be found?
Yes
I believe that all supported characters are included within MAPPING so it would have no affect here?
In
MAPPING
are only characters up to ASCII code 127. So this code block would work for characters 128-255. Not sure how much it is helpful. I think only character which can benefit from it isß
Ah yes, of course.
Do you think it'd be worth adding these to the output.txt? We should at least have a test case for some.
Merged PR #88 included these changes.
Make use of ISO-8859-1 escape notation (
\XXX (where XXX is 1–3 octal digits; range of 0–377)
)