184_notes:troubleshooting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Last revisionBoth sides next revision
184_notes:troubleshooting [2022/04/20 16:12] – created woodsna1184_notes:troubleshooting [2022/05/06 22:05] woodsna1
Line 1: Line 1:
 ====== Coding: When it all Goes Wrong ====== ====== Coding: When it all Goes Wrong ======
-A programming project isn't complete without an error that seems impossible to fix. Glowscript's error messages can be vague. If you find yourself completely lost in a coding project, the best bet is usually to take a step back. Go back to your pseudocode and comments, and compare them to the code you have written. Is each line doing exactly what it should be? Be particularly careful with loops and if statements, consider the location of each line within a loop.+A programming project isn't complete without an error that seems impossible to fix. Glowscript's error messages can be vague. If you find yourself completely lost in a coding project, the best bet is usually to take a step back. Go back to your pseudocode and comments, and compare them to the code you have written. Is each line doing exactly what it should be? Be particularly careful with loops and if statements, and consider the location of each line within a loop.
  
 ===== Debugging ===== ===== Debugging =====
 Often, something you've written isn't doing what you expect it to. The best way to track these issues down in Glowscript is using print() statements. Pick a value, and print it out. Then check if the printed value matches what you expect. Try a few if you're having trouble tracking down an error.  Often, something you've written isn't doing what you expect it to. The best way to track these issues down in Glowscript is using print() statements. Pick a value, and print it out. Then check if the printed value matches what you expect. Try a few if you're having trouble tracking down an error. 
-Sometimes, the issue is with the way your code is written. These cases can be particularly hard to track down.+ 
 +Another good strategy is to comment out code that you suspect is causing an error, then add it back in line-by-line until you find the source of the error. 
 + 
 +Sometimes, the issue is with the way your code is written (syntax). These cases can be particularly hard to track down.
 ==== Math ==== ==== Math ====
 Some common issues show up in math syntax Some common issues show up in math syntax
  • 184_notes/troubleshooting.txt
  • Last modified: 2022/05/06 22:06
  • by woodsna1