Open uzielmperez opened 5 years ago
@uzielmperez do you by chance have outdated code? because they made this change a few weeks ago: e8f27c9
@sshock Hi Phillip! I guess I was mostly referring to the sample output as shown in the readme for this repository. It looks like the readme's sample output might still include the outdated values (it's the very last item in the readme).
I'm already embarrassed about bringing this up haha, it's only that this really confused me when I was trying to map out the example manually (I wasn't able to use the emulator at first). I was using the readme's output as my only reference, my rock in a sea of logical uncertainty.
@uzielmperez Oh, nothing to be embarrassed about. I didn't even notice this in the readme, but yeah, it should be updated too.
@joshbodily Can you update this in the readme?
-MEMORY 0x37,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x3,0x8 +MEMORY 0x37,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0
Yes. I’ll update
On Tue, Apr 9, 2019 at 2:10 PM Phillip Hellewell notifications@github.com wrote:
@uzielmperez https://github.com/uzielmperez Oh, nothing to be embarrassed about. I didn't even notice this in the readme, but yeah, it should be updated too.
@joshbodily https://github.com/joshbodily Can you update this in the readme?
-MEMORY 0x37,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x3,0x8 +MEMORY 0x37,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mxenabled/mxcpu/issues/4#issuecomment-481415759, or mute the thread https://github.com/notifications/unsubscribe-auth/AGoY8A6OFaC0OACSahufKYEVnSobssp3ks5vfPOZgaJpZM4ci5n5 .
See #5 for Node.
readme updated in #8
Encountered "ReferenceError: readFile is not defined" when trying to run the emulator using Node.js (I had some trouble installing rhino).
Note: When mapping out the sample problem (sum of 1-10), I couldn't figure out why the sample output in the README.md shows a value for memory slots 0x0E and 0x0F (0x3 and 0x8, respectively). Maybe these values carried over unintentionally from the first exercise?
Cool stuff! :)