Explore >> Select a destination
|
You are here 
|
steakenthusiast.github.io | ||
| | | | |
ariya.io
|
|
| | | | | A common approach to analyze JavaScript source statically is to parse the source into an abstract syntax tree (AST) and then to traverse the AST. An alternative approach that might work in a few cases is to inspect each syntax node as it is constructed. | |
| | | | |
antoinevastel.com
|
|
| | | | | Example of a simple homemade JavaScript obfuscator applied on a security fingerprinting script. | |
| | | | |
patshaughnessy.net
|
|
| | | | | ||
| | | | |
coredumped.dev
|
|
| | | In this post, we are going to take a deep dive into pointer tagging, where metadata is encoded into a word-sized pointer. Doing so allows us to keep a compact representation that can be passed around in machine registers. This is very common in implementing dynamic programming languages, but can really be used anywhere that additional runtime information is needed about a pointer. We will look at a handful of different ways these pointers can be encoded and see how the compiler can optimize them for diff... | ||
