Skip to content
Commits on Feb 11, 2013
  1. @citizenmatt

    End of line normalisation

    citizenmatt committed Feb 11, 2013
Commits on Jan 23, 2013
  1. @citizenmatt

    Fixing lexer tests (apart from bang keywords)

    Gold files missing end of line marker at end of file, FSharpParser now
    derives from FSharpParserGenerated. Bang keyword tests still not
    working.
    citizenmatt committed Jan 23, 2013
  2. @citizenmatt

    Allow running tests with plugins installed

    By default, ReSharper's test framework uses the normal ReSharper user
    settings folders when loading an environment to run tests, and this will
    load any plugins you normally have installed, which can cause tests to
    fail. This change will make it use a different folder, so plugins don't
    get loaded
    citizenmatt committed Jan 23, 2013
  3. @citizenmatt

    Tweaked empty constants to fix code gen

    Changed emptyList, emptyAray and unit to be private nonterminals (so
    they don't appear as types in the parse tree, and the rules are pulled
    up into rule usage). This fixes the code gen for constantExpression and
    constantPattern, which both expose a value that is either a constant
    leaf token, or one of these empty types. Not sure this is right (might
    be better to introduce a private aux composite to hold all of these
    things, and still keep the code gen happy).
    
    On the plus side. Clean compile!
    citizenmatt committed Jan 23, 2013
  4. @citizenmatt

    Removed generated file

    citizenmatt committed Jan 23, 2013
  5. @citizenmatt
  6. @citizenmatt

    Fixing up unresolved tokens

    Removed OPERATOR_ tokens. Will add them back in if/when we need them.
    Added CARET token, by hand (but updated tokens.xml too)
    citizenmatt committed Jan 23, 2013
  7. @citizenmatt

    Added empty base classes

    Working towards a clean compile, but might be better to remove and add
    back if/when we need them
    citizenmatt committed Jan 22, 2013
  8. @citizenmatt

    Remove custom implementations flag

    Until such time as we need to derive from the normal implementation,
    let's just stick to the original
    citizenmatt committed Jan 22, 2013
  9. @citizenmatt
  10. @citizenmatt
  11. @citizenmatt
  12. @citizenmatt
  13. @citizenmatt

    Use IFSharpIdentifier instead of IIdentifierNode

    Further reducing compilation errors
    citizenmatt committed Jan 22, 2013
  14. @citizenmatt

    Replaced KEYWORD_XX_OP with symbol token

    Reducing compilation errors
    citizenmatt committed Jan 22, 2013
  15. @citizenmatt

    Using XXX_KEYWORD instead of KEYWORD_XXX

    Use the name of the keyword token defined in tokens.xml
    citizenmatt committed Jan 22, 2013
  16. @citizenmatt

    Removed all semantic directives from fsharp.psi

    Semantic interfaces are no longer supported by ReSharper - the semantic
    interfaces merged with the main parse tree several years ago. Reduces
    compile errors.
    citizenmatt committed Jan 22, 2013
  17. @citizenmatt
  18. @citizenmatt
  19. @citizenmatt

    Code is now generated in the "correct" structure

    THE CODE NO LONGER COMPILES!!
    
    The ParserGen msbuild targets expects the generated code to live under Gen/Psi/Language/ and Gen/Parsing/Language. As part of the process, it removes anything under Gen, then re-adds anything in Gen/Psi/FSharp and Gen/Parsing/FSharp.
    
    Unfortunately, all of the files have errors, so the code no longer compiles.
    citizenmatt committed Jan 16, 2013
Something went wrong with that request. Please try again.