|
Part 1
Jan 28, 2002 23:41:26 GMT -5
Post by Sylph on Jan 28, 2002 23:41:26 GMT -5
this assignment is too long, and too hard. i didn't really understand a8 from 108.. damn memory models.. for the printouts they gave us, we wouldn't be erasing anything, right? how do u use the little box to store something that is being returned, the one that stacks on top of a method stack? how do u know when to pop/erase a method box? i don't like this assignment..
|
|
|
Part 1
Jan 29, 2002 14:26:26 GMT -5
Post by 1.8T on Jan 29, 2002 14:26:26 GMT -5
I feel the same way i dunno about u guys. but i'm having trouble following wut my prof does during the lecture., its sooo confusing + the fact he can't write properly., and he's like rushing through this stuff pretty quick.,,..,
|
|
|
Part 1
Feb 5, 2002 23:39:11 GMT -5
Post by Sylph on Feb 5, 2002 23:39:11 GMT -5
when trying to reduplicate the memory model, is anyone else stuck in an infinite loop? any pointers?
|
|
|
Part 1
Feb 5, 2002 23:58:34 GMT -5
Post by Observer on Feb 5, 2002 23:58:34 GMT -5
Unfortunately, the best way to probably understand it to read through and fully understand the lecture notes from page 37 to 78. It's all there but terribly written and all over the place (they will give examples and tell you do something but then actually explain how to do it a few pages later!). I suggest trying the TestFrac example and seeing if you were able to draw the stuff on pages 71-74 yourself. Method call (the hardest to figure out how to draw) is explained on page 65.
Is part two harder than part one?
|
|
|
Part 1
Feb 6, 2002 0:01:32 GMT -5
Post by Sylph on Feb 6, 2002 0:01:32 GMT -5
no; i think part 1 is waaayyy harder, cuz we had no practise w/ it.
|
|
|
Part 1
Feb 6, 2002 15:09:28 GMT -5
Post by Yingster on Feb 6, 2002 15:09:28 GMT -5
the whole assignment is hard!!
|
|
|
Part 1
Feb 6, 2002 23:24:23 GMT -5
Post by Sylph on Feb 6, 2002 23:24:23 GMT -5
hooray! ^_^ my part 6 tracing matches up w/ the memory model they gave us! (i'm pretty sure)
tip: trace the way they teach us to trace. there isn't really a shortcut. but when doing the method stack, u should label the method's address (the address of instance that is performing the method) even though it's not conventional. u gotta do this or else u'll get screwed up, unless u have perfectly infallible short term & long term memory + perfect concentration..
|
|