Skip to content
Commits on Nov 7, 2015
  1. @dbluelle
  2. @dbluelle
Commits on Nov 6, 2015
  1. @dbluelle
  2. @dbluelle

    remove unneeded log output

    dbluelle committed
  3. @dbluelle
  4. @dbluelle
  5. @dbluelle
  6. @dbluelle
  7. @dbluelle
Commits on Nov 5, 2015
  1. @dbluelle

    [XMLNode] fix appendChild

    dbluelle committed
  2. @dbluelle
  3. @dbluelle
Commits on Nov 4, 2015
  1. @dbluelle
  2. @dbluelle
  3. @dbluelle
Commits on Nov 3, 2015
  1. @dbluelle
  2. @dbluelle
Commits on Nov 1, 2015
  1. @dbluelle
  2. @dbluelle
  3. @dbluelle
Commits on Oct 10, 2015
  1. @dbluelle
  2. @dbluelle
  3. @dbluelle
  4. @dbluelle
Commits on Oct 3, 2015
  1. @dbluelle

    [ASObject] fix serialize

    dbluelle committed
Commits on Oct 2, 2015
  1. @dbluelle
  2. @dbluelle

    Merge pull request #256 from jobermayr/master

    dbluelle committed
    Compiler Improvements
  3. @dbluelle
  4. @dbluelle
  5. @dbluelle
  6. @dbluelle
Commits on Oct 1, 2015
  1. @aajanki

    Merge pull request #259 from adrianherrera/bugfix/parse-int

    aajanki committed
    Bug fix in string to int parse code
  2. @adrianherrera

    Bug fix in string to int parse code

    adrianherrera committed
    If the string to parse is "0" (or "00", "000", "0000...", etc.) then after all
    the "leading zeroes" have been skipped, cur and end will point to the same
    location, causing the function to return false.
    
    To fix, check if we have reached end-of-string after skipping the leading
    zeroes. If we have reached the end of the string and this is not an empty
    string (i.e. count > 0) then the parsed integer has value 0 and we can return
    true.
Commits on Sep 30, 2015
  1. @jobermayr

    Fix more compiler warnings.

    jobermayr committed
  2. @jobermayr
Something went wrong with that request. Please try again.