start of an eclipse based java tutorial #291
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think the function names should be standard, and you should just use comments instead. |
|
I am going to close this as it is not ready yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was thinking about something like this.
There should be some help for setting up the environment (install eclipse, pull from the repository, open project), and using this (run the project as junit test, and make them green one by one).
Also, pressing "proceed" on the "errors on workspace" dialog teaches bad practice, but I have no idea how to write syntactically valid code for testing creation of a local variable. Maybe variable declaration should be started with fields, and the unit tests could use reflection to check.