Handling Quartus executable return codes

Just a comment, but just because the GUI seems strange, take the time to delve into it some. Lauching compiles makes perfect sense for a script, but the Quartus GUI has a lot of really nice things. Even something that seems good for text like the reports are nice in the GUI. The hierarchical utilization sections have +/- by each hierarchy so you can roll everything up and make it more readable. Going to the Fitter -> Resource Section -> Control SIgnals and being able to sort by hierarchy or Usage and you can find how many clock enables in a particular section, or all the asynchronous clears. Go to the Fitter RAM summary and sort by MLAB usage and find exactly which RAMs use MLABs, which use M9Ks, etc. Cross-probing is huge too. Double-click on an error in synthesis and that HDL file pops up at the line number with the error. Right-click Locate on that signal and you can find it in the Pin Planner to see where it's assigned, or in the Assignment Editor to see if it has any other assignments. Highlight a bunch of failing paths in TimeQuest, right-click Locate to Chip Planner, and you can see them drawn out across the die. There are all sorts of niceties that you would never find going through the text files.