It tracks how many trial runs you did on your code.

134 trials...


Way to let me know I'm a slow learner with assembler. This shit sucks trying to make it efficient and learning it distance ed.

10/27/2011 11:48:34 AM

does your number of trials affect your grade in anyway? cause that shit is just wrong.

10/27/2011 11:50:23 AM

you may suck, but it will burn even worse when someone in your section does the entire assignment in 3 lines.

10/27/2011 11:50:52 AM

Haha, no, it doesn't affect your grade at all. Just a reminder how much of a failure I am lol .

10/27/2011 11:50:58 AM

or maybe it shows how determined you are to get it just right?

10/27/2011 11:52:00 AM

whoa chit chat is study hall #2

10/27/2011 11:52:25 AM

Just wait till next week when he announces Bob did his code in 1 line and 2 trial runs

10/27/2011 11:52:52 AM

Maybe I'm missing something, but if you're just submitting code, how does it know?

10/27/2011 11:53:49 AM

You don't submit the code. You run it in this program that grades it and gives you a print out. You submit that.

10/27/2011 11:55:03 AM

[Edited on October 27, 2011 at 11:56 AM. Reason : trial]

10/27/2011 11:55:56 AM

He has a little program that you feed your code into that runs it and checks for expected behavior and produces a grade on the spot, then uploads it to his gradebook (or something like that).

It tracks runs, accuracy, etc. I seem to remember about everything being automated.

10/27/2011 11:56:09 AM

in CSC 234/236, your programs are graded on your own machine with a grading program. It also has a program that will take your code and run it through test cases. It's actually really useful and I like this way of grading programs a lot.


I'm just glad it doesn't track how many times I tried to assemble my code unsuccessfully.

10/27/2011 11:56:14 AM

Quote :

"MOUSE IN MAZE"

10/27/2011 11:58:49 AM