Timeline for Code requiring a third-party pre-processor to make it work
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2014 at 0:45 | comment | added | trichoplax is on Codidact now | Reviewing Python code doesn't require installing Python. If you're familiar with the language you can review it regardless. If you're not familiar with the language the python tag helps exclude such questions. I think a lombok tag is the way to go, so only people who are already comfortable reviewing lombok code will consider such questions. | |
| Mar 13, 2014 at 12:08 | history | edited | 200_success | CC BY-SA 3.0 |
Added CoffeeScript analogy
|
| Mar 13, 2014 at 3:35 | comment | added | 200_success | Lombok claims, On javac: Include lombok.jar on the classpath as you compile. That's all there is to it! If your IDE introduces complications to that simple process, that's your own problem, and you're free to choose a different question to review. The code in the question is still valid. | |
| Mar 13, 2014 at 3:09 | comment | added | rolfl | Put a different way, you need to reconfigure your development environment to review the code. This includes your IDE, and your compile tool-chain. That is in addition to adding a jar to the classpath for the code you are going to review.... unless you are already familiar with the pre-processor, and you don't need to compile/test the code to review it. | |
| Mar 13, 2014 at 3:05 | comment | added | rolfl | As an opposing point, the statement "...all you have to do is include it in your classpath when compiling..." is woefully understating the issue. You need to 'install' the preprocessor as an extension to Eclipse (whatever IDE you use), and you need to run pre-processing steps before you can 'just compile it'. | |
| Mar 13, 2014 at 2:59 | history | answered | 200_success | CC BY-SA 3.0 |