-
Notifications
You must be signed in to change notification settings - Fork 26
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
[AB3: Tracing Code] Breakpoint in main method #33
Comments
hmm... the tutorial doesn't actually ask the reader to put a breakpoint in the main method. It's just a hypothetical statement. Is there a way to make it clearer (and avoid possible confusion)? |
Will the following phrasing be better? Proposed: |
@tayruxin 🤔 hmm... I'm not sure. If we improve the page on debugging (given below) I imagine most students might be OK with the current version without further elaboration. In any case, I took another pass at revising the text in that section. Can you take a look here and share what you think? I revised the content up to the Intellij code search screenshot. |
I believe the revised text makes the paragraph more coherent. Thank you for the revision. |
Current:
Problem:
Students might not know what to expect after setting a breakpoint at the first statement of the main method.
Proposed:
Insert the following paragraph at the end, to show the result of putting a breakpoint in the first statement of the main method:
Upon running the application with the breakpoint in the first statement of the main method, you will realize that the app is launched via this method.
The text was updated successfully, but these errors were encountered: