New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal remove ANTLR from source #5364
Comments
Removing the preprocessor would break nearly all code in the examples and on the site, there's simply no way we're going to do that. If you know how to compile on the command line, or use an IDE, and want those language features, then use them. We've designed Processing to work in different environments this way; you don't have to use the PDE itself. |
Ok, thank you. Just summerize what everyone else is thinking, if you follow this hole topic and threads, i'm not the only one who requested some changes here. To have a heavyweight MB dependency and not a guy around, who into thouse stuff, nearby to make recent updates, seems not a good choice for me. |
That has nothing to do with what I wrote. I'll repeat:
|
@benfry
It don't has to be that simple. But i totaly okay, with it. Best 🌞 |
#3054
Ongoing story since 3 Years zero development, and we are in beta for Java 10 and can't use simpel Java 8 features in Processings IDE. What more to say.
I use Processing for very small scetches to relax and have fun. I think many users do. For newbies their could be and an warning msg: "Check your code". We can also phrase the "default" Java SDK jdb to extract the line nummer to a String msg: "look closer at Line 9 ". Maybe an emoj somewhere (optional) 🌞.
Check this out it works in my browser.
http://es6-features.org/#Constants
if i use the native Java compiler java -cp * Code.java | jar -cf exe.jar *.class | java -cp * Code and have a bug, the phraser will print me the point where the error occur into my console window. Maybe it is possible to use a simpel String method to print that message into Processing IDE
Maybe their is also a simple hack to ANTLR, when ANTLR would sees something from Java 8 just igonere it in processsing.
The text was updated successfully, but these errors were encountered: