1. 22 Dec, 2014 5 commits
  2. 21 Dec, 2014 2 commits
  3. 20 Dec, 2014 3 commits
  4. 19 Dec, 2014 5 commits
  5. 17 Dec, 2014 3 commits
  6. 16 Dec, 2014 3 commits
  7. 15 Dec, 2014 1 commit
  8. 14 Dec, 2014 5 commits
  9. 10 Dec, 2014 4 commits
  10. 09 Dec, 2014 5 commits
  11. 08 Dec, 2014 2 commits
    • albert-github's avatar
      Fortran color code of END · 1cfa914c
      albert-github authored
      The color for the single END in Fortran code was of the color of the flow type entities though for all the flow entities the entity name is mandatory. For the entity statements of some keywords e.g. SUBROUTINE and FUNCTION the entity name is not mandatory with the END statement. The color of the single END statement has been changed from the flow type to the normal keyword type.
      1cfa914c
    • albert-github's avatar
      Fortran continuation character seen as begin of function call · b2e9aa36
      albert-github authored
      In case in fixed format code a line like:
      "     x   ( " existed and the x was on position 6 the "x   (" was seen as the start of a function call.
      b2e9aa36
  12. 07 Dec, 2014 2 commits
    • albert-github's avatar
      Support for INLINE_SOURCES in Fortran · 940a802a
      albert-github authored
      Fortran does not yet support the INLINE_SOURCES, with this patch (part of) this omission is solved.
      940a802a
    • albert-github's avatar
      Extra empty line in source fragments · 79b40a43
      albert-github authored
      In case of a language that does not uses curly brackets to define blocks (such as Fortran) there was a newline character in the variable c and this was written in the "code fragment" buffer and subsequently written to the output resulting in and extra empty line on top. I languages using curly brackets this is later overwritten by the while loop searching for the open curly bracket.
      79b40a43