1. 03 Mar, 2014 2 commits
  2. 26 Feb, 2014 3 commits
  3. 22 Feb, 2014 1 commit
  4. 16 Feb, 2014 2 commits
  5. 15 Feb, 2014 2 commits
    • Damien George's avatar
      Implement proper exception type hierarchy. · c5966128
      Damien George authored
      Each built-in exception is now a type, with base type BaseException.
      C exceptions are created by passing a pointer to the exception type to
      make an instance of.  When raising an exception from the VM, an
      instance is created automatically if an exception type is raised (as
      opposed to an exception instance).
      
      Exception matching (RT_BINARY_OP_EXCEPTION_MATCH) is now proper.
      
      Handling of parse error changed to match new exceptions.
      
      mp_const_type renamed to mp_type_type for consistency.
      c5966128
    • Damien George's avatar
      Change mp_obj_type_t.name from const char * to qstr. · a71c83a1
      Damien George authored
      Ultimately all static strings should be qstr.  This entry in the type
      structure is only used for printing error messages (to tell the type of
      the bad argument), and printing objects that don't supply a .print method.
      a71c83a1
  6. 12 Feb, 2014 1 commit
  7. 10 Feb, 2014 2 commits
  8. 08 Feb, 2014 4 commits
  9. 06 Feb, 2014 1 commit
  10. 05 Feb, 2014 1 commit
  11. 02 Feb, 2014 4 commits
  12. 01 Feb, 2014 1 commit
    • Paul Sokolovsky's avatar
      Implement default function arguments (for Python functions). · 90750029
      Paul Sokolovsky authored
      TODO: Decide if we really need separate bytecode for creating functions
      with default arguments - we would need same for closures, then there're
      keywords arguments too. Having all combinations is a small exponential
      explosion, likely we need just 2 cases - simplest (no defaults, no kw),
      and full - defaults & kw.
      90750029
  13. 29 Jan, 2014 1 commit
    • Damien George's avatar
      py: Simplify fastn in VM; reduce size of unique code struct. · d0691cca
      Damien George authored
      We still have FAST_[0,1,2] byte codes, but they now just access the
      fastn array (before they had special local variables).  It's now
      simpler, a bit faster, and uses a bit less stack space (on STM at least,
      which is most important).
      
      The only reason now to keep FAST_[0,1,2] byte codes is for compressed
      byte code size.
      d0691cca
  14. 28 Jan, 2014 2 commits
  15. 26 Jan, 2014 1 commit
  16. 25 Jan, 2014 2 commits
  17. 24 Jan, 2014 1 commit
  18. 22 Jan, 2014 1 commit
  19. 21 Jan, 2014 1 commit
  20. 20 Jan, 2014 2 commits
  21. 19 Jan, 2014 5 commits