8 ms·

Here's a wiki link[0] for anyone else that didn't know what they were looking at. 0: https://en.wikipedia.org/wiki/DONKEY.BAS https://en.wikipedia.org/wiki/DON

Here's a wiki link[0] for anyone else that didn't know what they were looking at. 0: https://en.wikipedia.org/wiki/DONKEY.BAS https://en.wikipedia.org/wiki/DONKEY.BAS

vmarsy 10y ago
> "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
- Artoemius 10y ago
  > The first version of DONKEY.BAS was released in 1981, followed by version 1.10 in 1982 This is the improved 1982 version.
  - vmarsy 10y ago
    I see. I thought they'd have kept the authors name, unless the code was completely rewritten.
  - Buge 10y ago
    Even in the 1.00 version here it doesn't have Gates in the comments. http://www.pcjs.org/devices/pcx86/machine/5150/cga/64kb/donkey/ http://www.pcjs.org/devices/pcx86/machine/5150/cga/64kb/donk...
- pythonistah 10y ago
  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.
  - colejohnson66 10y ago
    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?
    - allenu 10y ago
      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.
      - kqr 10y ago
        "Correct" order is ambiguous to someone asking that question in the first place.
        colejohnson66 10y ago
        It sounds like he's saying the "line number" is just the index to a tokenized list (i.e. line 15 is at `lines[15]') where unused lines are just nops. So my "program" would be tokenized and the lines stored like: char** lines = malloc(...); lines[10] = &line1; lines[30] = &line2; lines[20] = &line3; Then when executing, it starts at `lines[0]', sees nops, gets to `lines[10]' and runs it, sees more nops, gets to `lines[20]' and jumps to `lines[10]'. All the while ignoring `lines[21]' and up.
        abecedarius 10y ago
        Usually in 8-bit BASICs the lines would be stored consecutively (not in separate malloced segments) with each line starting with its line number. Yes, this meant that GOTO required a search. Memory was a really central design constraint on these systems. I don't know how closely MS's BASICA on the PC followed this model, but the PC's starting configuration had 16k bytes of RAM.
- rurban 10y ago
  Microsoft usually started at 1000 So you can see that they added the copyright and SAMPLES$ logic later.

Here's a wiki link[0] for anyone else that didn't know what they were looking at. 0: https://en.wikipedia.org/wiki/DONKEY.BAS https://en.wikipedia.org/wiki/DONKEY.BAS

vmarsy 10y ago

> "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

Artoemius 10y ago
> The first version of DONKEY.BAS was released in 1981, followed by version 1.10 in 1982 This is the improved 1982 version.
- vmarsy 10y ago
  I see. I thought they'd have kept the authors name, unless the code was completely rewritten.
- Buge 10y ago
  Even in the 1.00 version here it doesn't have Gates in the comments. http://www.pcjs.org/devices/pcx86/machine/5150/cga/64kb/donkey/ http://www.pcjs.org/devices/pcx86/machine/5150/cga/64kb/donk...
pythonistah 10y ago
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.
- colejohnson66 10y ago
  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?
  - allenu 10y ago
    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.
    - kqr 10y ago
      "Correct" order is ambiguous to someone asking that question in the first place.
      - colejohnson66 10y ago
        It sounds like he's saying the "line number" is just the index to a tokenized list (i.e. line 15 is at `lines[15]') where unused lines are just nops. So my "program" would be tokenized and the lines stored like: char** lines = malloc(...); lines[10] = &line1; lines[30] = &line2; lines[20] = &line3; Then when executing, it starts at `lines[0]', sees nops, gets to `lines[10]' and runs it, sees more nops, gets to `lines[20]' and jumps to `lines[10]'. All the while ignoring `lines[21]' and up.
        abecedarius 10y ago
        Usually in 8-bit BASICs the lines would be stored consecutively (not in separate malloced segments) with each line starting with its line number. Yes, this meant that GOTO required a search. Memory was a really central design constraint on these systems. I don't know how closely MS's BASICA on the PC followed this model, but the PC's starting configuration had 16k bytes of RAM.
rurban 10y ago
Microsoft usually started at 1000 So you can see that they added the copyright and SAMPLES$ logic later.