The Human CPU Experiment

Do you take your computer for granted? Have you ever wondered what it must belike to be your computer? Now you can try it. (Some programming experience maybe required to get the most out of this game.)

I really like the steadily increasing difficulty of it. Towards the end it gets really creative doing boolean operations on base 4 numbers with two calculations on the stack. And for the CHR$/ASC conversions, that's just guessing for me.

For the hiscore table. The only one I don't recognize is MCP - are you really referring to Microsoft Certfied Professional?

edit: looking at the source code, I'm taken by the use of unicode in variable names:

I just got E4D9, which makes me feel beating Data is just about achievable on a good day with some practice.

When I was tired from staying up all night, I couldn't get close. The tiredness was a bit of a problem given I was trying to balance the scoring so that beating all the robots was a good balance of challenging but achievable. I think I must have got it about right though, at least for us lot.

Text based math game with old monochrome feel. Had 2 gos. First until it started asking me mod questions, then I ran out of time. Second, I ignored the mod, then the hex, then the Binary and I noticed your particle engine kicked in. Well done mate, very good effort.

As always, D is a breath of fresh air. Basic conveniences like GC built into the language, not to mention random acts of syntactic sugar all over the place (like $ inside [] to refer to the length of the current array). I do of course have one or two reservations about it as a serious language: difficulty avoiding the GC if you need to, and a slight case of 'only one compiler really works so far'. That's DMD, and while it excels on executable size, it isn't the best for generated code speed. Then again, these things are always improving. There's also Visual D which helps a lot with the editing process, although one or two things could be slightly nicer with very little effort (like autocomplete looking at substrings anywhere instead of only matching the beginning). One other thought is that you do have to know D's semantics, and if you aren't entirely clear, it's possible to shoot yourself a bit (e.g. 'foreach' loops if you don't know to use 'ref' at the right times). A language like C# might be marginally better in that regard because the spec is smaller. But compared to C/C++ in terms of language usability - no contest. (Of course C/C++ have widespread support and tooling on their side though, despite STILL requiring header files - really, in this day and age? Why wasn't it C++11's PRIMARY focus to get rid of those monumental wastes of time?)

Crashes right away with an access violation.{"name":"609556","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/f\/6\/f67be5faf2f19b27ecc958abe7eb5bc5.png","w":294,"h":165,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/f\/6\/f67be5faf2f19b27ecc958abe7eb5bc5"}

I don't have a working D compiler installed so I can't really test it further. gdb fails to recognize it as an executable file format it knows.

@Bruce PerryI don't mind headers so much in C, I view them as a necessary evil of the compiler/linker dichotomy, but they are THE primary reason I hate using C++. Want to write a library in C++? Good luck hiding your dependencies from the outside world because all your private members have to go in the public header! (I realize the pimpl idiom solves this, but it should be built into the language.)

The biggest problem with C++, I think, is that it strives for backward compatibility with C at all costs. It would benefit greatly from breaking that shackle, I think.

Edgar, sorry to see that. You did extract it from the zip before running it, I assume? Shame there's no stacktrace - there normally would be, under the dashes. If you do have time, you might be able to install Visual Studio 2013 Community Edition (it's free) and attach it as a debugger and find out more. You might even not need D, although you will probably have to start it with the debugger attached (somehow) rather than running it and attaching later.

Mark, how did you do with your cheats in place? Did you get to some questions you weren't prepared for?