21–30 of 183 posts
Earlier quoted context omitted.
I'm disappointed that my iPhone can't drive the car because Apple didn't put directional keys on the onscreen keyboard.
spacebar works (it's the only key needed).
It's not surprising that this simulation of a 36 year old 4.77Mhz desktop runs fine in javascript on my 1.3GHz quadcore $40 phone... but in a way, it is.
Earlier quoted context omitted.
> "We were surprised to see that the comments at the top of the game proudly proclaimed the authors: Bill Gates and Neil Konzen." This is odd that these comments aren't in the github source code, is it missing something? Why does it starts at line 940? 940 REM The IBM Personal Computer Donkey 950 REM Version 1.10 (C)Copyright IBM Corp 1981, 1982 960 REM Licensed Material - Program Property of IBM
> The first version of DONKEY.BAS was released in 1981, followed by version 1.10 in 1982 This is the improved 1982 version.
http://www.pcjs.org/devices/pcx86/machine/5150/cga/64kb/donk...
Earlier quoted context omitted.
Could line numbers be out of order? Like, if I did this: 10 PRINT "1" 30 PRINT "2" 20 GOTO 10 What would print out? Just a bunch of "1"s or "12"s?
It gets run in the correct order. Think of each line as a command that stores the instruction immediately at that line number. You could actually "re-type" a line later by reusing the same line number but replacing it with new contents.
Earlier quoted context omitted.
Could line numbers be out of order? Like, if I did this: 10 PRINT "1" 30 PRINT "2" 20 GOTO 10 What would print out? Just a bunch of "1"s or "12"s?
It gets run in the correct order. Think of each line as a command that stores the instruction immediately at that line number. You could actually "re-type" a line later by reusing the same line number but replacing it with new contents.
Earlier quoted context omitted.
Could line numbers be out of order? Like, if I did this: 10 PRINT "1" 30 PRINT "2" 20 GOTO 10 What would print out? Just a bunch of "1"s or "12"s?
It gets run in the correct order. Think of each line as a command that stores the instruction immediately at that line number. You could actually "re-type" a line later by reusing the same line number but replacing it with new contents.
Playable here: http://www.pcjs.org/devices/pcx86/machine/5150/cga/64kb/donk... "The above simulation is configured for a clock speed of 4.77Mhz, with 64Kb of RAM and a CGA display, using the original IBM PC Model 5150 ROM BIOS and CGA font ROM. This configuration also includes a predefined state, with PC-DOS 1.0 already booted and DONKEY.BAS ready to run. And now that PCx86 automatically saves all your changes (subje…
I'm disappointed that my iPhone can't drive the car because Apple didn't put directional keys on the onscreen keyboard.
Andy Hertzfeld recollects how Macintosh team dissected the new IBM PC and what they thought of donkey.bas: http://www.folklore.org/StoryView.py?project=Macintosh&story...
Every piece of software he's written has been a second rate failure.
Earlier quoted context omitted.
The line numbers in BASIC were arbitrary. People often started at higher numbers and jumped by 10 in case they had to put code or comments before or between lines.
Could line numbers be out of order? Like, if I did this: 10 PRINT "1" 30 PRINT "2" 20 GOTO 10 What would print out? Just a bunch of "1"s or "12"s?
The thing is that basic programs were not entered through a 2D text-editor per rather line per line. You would type "LIST" to re-read the whole program you typed so far, with the lines in the correct order. Then, you would enter a line starting with a number. It would overwrite any existing line with the same number.
Typically, a way to correct the program you wrote would be to type:
30
15 PRINT "2"
(replace the line 30 by an empty line, and insert a line number 15)