From c3e7012f2d4cf752c54ad01d649d281bb4634ad1 Mon Sep 17 00:00:00 2001 From: Loic Nageleisen Date: Sun, 8 Apr 2012 20:16:57 +0200 Subject: [PATCH] Updated doc --- README.mdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.mdown b/README.mdown index 75bf769..75ceda5 100644 --- a/README.mdown +++ b/README.mdown @@ -2,13 +2,13 @@ A DCPU-16 implementation in Python. See [the spec][0]. -# But what's the goal of this? There's another one already! +# What's the goal of this? -Well, what's wrong with taking another stab at it? Besides, I personnally felt it was too C-ish, and not pythonic enough (whatever that means, but you should [read][1] [this][2]). I wanted to revive whatever low-level (admittedly limited) ASM knowledge I had (from 6800/68000) and sharpen my Python-fu. The spirit of the thing is to be educative for everyone (including me). +Many high-level implementations looked like C-in-other-language, so let's have a pythonic enough (whatever that means, but you should [read][1] [this][2]) implementation. The spirit of the thing is to be educative for everyone. # How do I use this? -It's meant to be used interactively via the Python REPL as well as programmatically. I might implement a specific ASM REPL at some point. +It's meant to be used interactively via the Python REPL as well as programmatically. A specific ASM REPL might be implemented at some point. An example of a Python REPL session: @@ -33,7 +33,7 @@ An example of a Python REPL session: # What is the status of this? -It's not bug-free yet, the implementation itself is still a WIP and the whole of the spec example does not pass yet. But hey, that's what you get in a few late hours. Fixes coming, I promise. +As of v1.0 the CPU implementation ought to be complete according to DCPU-16 spec v1.1. # Features