An error occurred fetching the project authors.
  1. 14 May, 2009 2 commits
  2. 04 May, 2009 1 commit
  3. 03 May, 2009 1 commit
  4. 23 Apr, 2009 2 commits
  5. 11 Mar, 2009 1 commit
  6. 07 Mar, 2009 1 commit
  7. 01 Mar, 2009 2 commits
  8. 20 Feb, 2009 1 commit
  9. 10 Feb, 2009 1 commit
  10. 07 Feb, 2009 1 commit
  11. 20 Dec, 2008 1 commit
  12. 19 Dec, 2008 1 commit
  13. 12 Dec, 2008 2 commits
  14. 25 Nov, 2008 1 commit
  15. 24 Nov, 2008 2 commits
  16. 14 Nov, 2008 1 commit
  17. 12 Nov, 2008 3 commits
  18. 11 Nov, 2008 2 commits
    • Stefan Behnel's avatar
      partial implementation of the "exec" statement · b8a099a0
      Stefan Behnel authored
      - only supports code in strings, not files (should be easy to add)
      - only the "exec XYZ in GLOBALS [,LOCALS]" form is supported, not the execution in the current namespace (would require a mapping representation of it)
      - also includes an incomplete (3-args only) and untested implementation for the exec() function in Py3
      b8a099a0
    • Robert Bradshaw's avatar
      more compiler cythonization · 99327e65
      Robert Bradshaw authored
      more balancing needs to be done.
      99327e65
  19. 17 Oct, 2008 1 commit
  20. 15 Oct, 2008 1 commit
  21. 08 Oct, 2008 1 commit
  22. 30 Sep, 2008 3 commits
  23. 18 Sep, 2008 1 commit
  24. 22 Aug, 2008 1 commit
  25. 16 Aug, 2008 4 commits
  26. 15 Aug, 2008 2 commits
    • Dag Sverre Seljebotn's avatar
      Changed compiler directive comment format · 2f022483
      Dag Sverre Seljebotn authored
      --HG--
      rename : tests/compile/c_options.pyx => tests/compile/c_directives.pyx
      rename : tests/errors/e_options.pyx => tests/errors/e_directives.pyx
      2f022483
    • Stefan Behnel's avatar
      Rewrite of the string literal handling code · 2e8a0084
      Stefan Behnel authored
      String literals pass through the compiler as follows:
      - unicode string literals are stored as unicode strings and encoded to UTF-8 on the way out
      - byte string literals are stored as correctly encoded byte strings by unescaping the source string literal into the corresponding byte sequence. No further encoding is done later on!
      - char literals are stored as byte strings of length 1. This can be verified by the parser now, e.g. a non-ASCII char literal in UTF-8 source code will result in an error, as it would end up as two or more bytes in the C code, which can no longer be represented as a C char.
      
      Storing byte strings is necessary as we otherwise loose the ability to encode byte string literals on the way out. They do not necessarily contain only bytes that fit into the source code encoding as the source can use escape sequences to represent them. Previously, ASCII encoded source code could not contain byte string literals with properly escaped non-ASCII bytes.
      
      Another bug that was fixed: in Python, escape sequences behave different in unicode strings (where they represent the character code) and byte strings (where they represent a byte value). Previously, they resulted in the same byte value in Cython code. This is only a problem for non-ASCII escapes, since the character code and the byte value of ASCII characters are identical.
      2e8a0084