Git Product home page Git Product logo

cb2's People

Contributors

dargaud avatar debugloop avatar simhnna avatar simonsmiley avatar

Watchers

 avatar  avatar  avatar  avatar

cb2's Issues

Remove output from tests

our tests should not print anything to stdout or stderr.

We should try to find a ways to use a flag passed via gradle to enable this "debugging output" so we can see it online

Improve error messages

  • Missing semicolons are reported missing on the next line
  • Integers that are out of range are not reported as such (rework grammar to read more and report a proper error?)

Communication

@Dargaud, @analogbyte
Repo in English oder doch auf deutsch?

I personally don't like writing code in German (or mixed). Don't care about how we communicate on github though...

About irc... It's not very practical if you're not always online.
I can offer bouncer accounts, or we can use something like slack ๐Ÿ˜

Open issues with code generation

Known errors:

  • overridden parameters should be transformed
  • implicit returns
  • static context for sysout calls
  • access to class variables from main method
  • some strings need escaping

Files that cause errors:

  • method_implicit_return.m
  • string_copied_from_pdf.m
  • member_access.m
  • beispiele_timm.m
  • pretty_much_everything.m
  • array_declaration.m

Update valid test files to pass prettyPrinter tests

To do this we have three options:

  1. ignore certain errors (empty lines, comments, ...)
  2. get rid of all these errors in our valid files
  3. mirror all our valid files to a prettyPrinter subdirectory that would strip them of comments and whitespace...

I don't think 1. is that easy to implement, 2 would be stupid as we would loose parts of our tests, so I think we should go for 3. It will be some work.. :-)

JavaCodeGeneratrion todos

  • rework print() calls to System.out.println()
  • fix main method to add public and static keywords
  • fix new expressions
  • fix array declarations

Make sure only correct main methods are transformed

We currently only check for the name to match main.
We should also check if the return type is void and the arguments are only a string array.

In that case we transform the method to the public static void main(String[] args) array. In all other cases it should be treated as a normal non-static method

the name of the argument obviously shouldn't matter

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.