This project is read-only.


May 5, 2013 at 7:15 PM
Edited May 5, 2013 at 9:12 PM
Ok we now need to test the hell out of the lexical analysis. clearosdev now is your chance to help out. I will create a exe for others to test the compiler.

All you need to do is:
  • download the binary version or download the source code and compile it.
  • create C# files for each feature of the language.
  • look at the Lexical Boundary Points Tab
  • check that the different columns are correct.
  • if you find a bug then create an issue in the issue tracker
    • Be as descriptive as possible
    • Make sure you explain the column values
May 5, 2013 at 7:24 PM
Edited May 5, 2013 at 7:24 PM
here's the binary version of the testing suite:
May 5, 2013 at 9:16 PM
when using * / in comment it show up on the lexical boundary point as a operater
May 5, 2013 at 10:14 PM
Is there a space between the '*' and the '/'?
May 5, 2013 at 10:18 PM
Also can you use the issue tracker. The you can submit file through if you prefer.
May 5, 2013 at 10:21 PM
I will work on making it easier to test the compiler.
May 5, 2013 at 10:23 PM
There was and wheren't spaces between them
May 5, 2013 at 10:31 PM
We need a test for just about every part of the language:
  • Comments
  • PreProcessor Directives
  • Punctuators
  • Literals
  • Operators
  • Keywords
  • Identifiers
May 6, 2013 at 4:05 AM
The developers console now has a reporting tool. So to submit a report simply:
  • open the cs file (if you haven't done that already)
  • click file->save report
  • select the folder you wish to save to
To tool will create a folder called Sharp(time)(date) and populate it. You then compress/archive this folder and attach it to the issue tracker in your reply or issue.

You can also use the open report feature to open an uncompressed/unarchived report folder.