<div dir="ltr">Which game are you doing?</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 1, 2014 at 10:28 PM, Casey Ransberger <span dir="ltr"><<a href="mailto:casey.obrien.r@gmail.com" target="_blank">casey.obrien.r@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Hi Blake. I can concur with some of your "rambling." In fact I do intend to do a rough translation of one of the games in the book. </div><div><br></div><div>What's great about printed BASIC listings of games is that they tend to be relatively short, so they're fun to reimplement. That said, before doing an implementation of something, it helps to understand the original program very well. Arguably, the best way to understand a small program is to type it in, and deal with whatever bugs crop up right?</div><div><br></div><div>I'd ideally be doing this in Squeak from the start, but I'm already into using an Apple IIGS emulator to get started.</div><div><div class="h5"><div><br>On Oct 1, 2014, at 11:09 AM, blake <<a href="mailto:dsblakewatson@gmail.com" target="_blank">dsblakewatson@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Heh. Those books are the "well" I go back to when learning new languages. (I have both in print and learned to program using them.)<div><br></div><div>That said:</div><div><br></div><div>The code in those books is truly, truly awful, by necessity, due to the limitations of the Basic interpreters of the time. It's easier to reverse-engineer the code based on the limited printouts than to figure out what's going on with the one-character variable names and GOTOs being the primary means of branching.<br></div><div><br></div><div>And with THAT said:</div><div><br></div><div>Something LIKE those books could be incredibly useful. The one thing they had that most environments today don't is that you could start really simple, get a product, and build really easily on it. The Transcript isn't quite up to the task, and it's a big leap from the transcript to a GUI.</div><div><br></div><div>Rambling aside, when you think about it, it's a pretty small language you could build a DSL for: Variable assignment, basic math, IF-THEN, GOTO and RND....it's all on one page: <a href="http://www.atariarchives.org/basicgames/showpage.php?page=i12" target="_blank">http://www.atariarchives.org/basicgames/showpage.php?page=i12</a></div><div><br></div><div>Just have the PRINT go to a 80x25 scrolling grid. Heh. Fun!</div></div>
</div></blockquote><blockquote type="cite"><div><span></span><br></div></blockquote></div></div></div><br><br>
<br></blockquote></div><br></div>