
- port from using bigint to bignum (it's more mantained, builds on current node.js etc.)
  the tricky part about that is getting binary and/or working on negative bignums under bigint

Portability 
   - Check if Function.name works on IE. If it doesn't instead checking for _ in callercode check for a custom property.

General stuff that helps all backends
    Write tests (to avoid implementing stuff in crazy ways)
    - nfarunalt
    - nqp::eoffh - EASY
    - nqp::isstr
    - nqp::getmessage
    - nqp::printfh in combination with nqp::getstdout(),nqp::getstderr()
    - add a test for nqp::index with three arguments to t/nqp/59-nqpop.t - EASY
    - a test for if cond() -> $value-of-cond {...} - EASY
    - nqp::ifnull

Improving the code quality (which is a bit less atrocious then before ) 
    - Write a nqptidy (or a p6tidy) to make sure the nqp code has a consistent style
    - Tricky and/or confusing bits of code should be identified so that they get commented

Build system
    - make install should install a nqp-js runner.

Portability
    - Get the build system to work on windows (haven't tried that yet)

Expand the HACKING file.
  (Asking question that pmurias will glady answer is the best way to do this)
