Updated.

icculus · Oct 2, 2000 · 6ece7b5 · 6ece7b5
1 parent 897ae43
commit 6ece7b5
Show file tree

Hide file tree

Showing 5 changed files with 17 additions and 24 deletions.
diff --git a/docs/about.txt b/docs/about.txt
@@ -3,20 +3,15 @@ VBslacker 0.0.1
 Designed with tender loving care by Ryan C. Gordon and Gregory S Read.
 
 vbSlacker is currently being hacked at on Linux in this specification:
-  - Red Hat 6.1
-  - glibc2.1
-  - kernel 2.2.13
+  - Red Hat 6.2
+  - glibc2.1.2
+  - kernel 2.4.0-testsomething.
   - ELF-binaries.
 
 (Also being hacked on WinNT 4.0 by Greg, and Win98 and Slackware 7 on Ryan's
  VAIO N505VE...whoa.)
 
-Win32 support is in place in...uh...most places, thanks to cygwin B20.1.
+Win32 support is in place in...uh...some places, thanks to CygWin.
 
 Warranty: If vbSlacker breaks, you get to keep both SHINY pieces!
 
-
-(If you are seeing this when running MAKE, you probably need to
- specify a target platform. Try: 'make linux' or 'make win32'...)
-
-
diff --git a/docs/adding_languages.txt b/docs/adding_languages.txt
@@ -3,18 +3,15 @@ vbSlacker was designed and written by English-speaking people.
 If you want vbSlacker to output German, Spanish, or whatever, you'll
 need to do some translating.
 
-To add a new language to BASIClib, take the file English.h, and translate
+To add a new language to BASIClib, take the file vbslacker.lang, and translate
 it. These are all the string literals in the program. There are directions
-in the file on how to do this. Rename the file to German.h (or whatever),
-and mail it back to the vbSlacker development team, currently residing at
-ryan_gordon@hotmail.com. They will plug it into the Language.h file, and
-add it to the distribution.
+in the file on how to do this. Then mail it back to the vbSlacker development
+team, currently residing at ryan_gordon@hotmail.com. They will plug it into
+the Language.h file, and add it to the distribution.
 
 Please note that you will be credited for your work, but otherwise not
 compensated. Immortality in the "contributions" documentation is all
 we can offer; sorry.
 
-!!! This will change with the BASIClibLang file...
-
 /* end of adding_languages.txt ... */
 
diff --git a/docs/adding_modules.txt b/docs/adding_modules.txt
@@ -54,11 +54,8 @@ extern "C" {
   internal-only modules, consider adding your header to StdBasic.h instead.
   Don't add it to both.
 
-- Compile with -D_REENTRANT and -DLINUX_THREADS (or -DSINGLE_THREADED),
-  -DLANG_ENGLISH (or whatever) and -DLINUX_I386 (or whatever) on the command
-  line, or better yet, read below for how to add your module to the makefiles...
-
-- Makefiles: Do this to "Makefile" in the BASIClib dir.
+- Makefiles: Do this to "Makefile.linux", "Makefile.win32", etc in the
+  BASIClib dir. (!!! we really need to unify the makefiles...)
 
   - On the "OBJS =" line, add your compiled module's filename: MyFunctions.o.
     If you have to add a new line to fit into 80 columns, add a backslash

diff --git a/docs/todo_mikey.txt b/docs/todo_mikey.txt
@@ -1,7 +1,11 @@
 (mikey's) TODO list:
 
+- Make vbslacker.cons parser handle multiple spaces.
+- Check entire codebase for "//" comments.
+- Put const qualifier wherever you can.
 - Split console drivers into individual shared libraries that are
   loaded/unloaded dynamically, in a config-file-specified hierarchy.
+- Check all code for possible replacements with _vbReleaseThreadThrowError().
 - errors should be their own type? Short?
 - autoconf.
 - __crashHandler();
@@ -11,7 +15,7 @@
 - Variant needs to become __vbVariant ...
 - PVariant needs to become __vbVariant * ...
 - Other constants need modifying...
-- What to do about: ActiveX
+- What to do about: ActiveX  (_vbComponent?)
 - What to do about all the damned constants?
 - What to do about variants?
 - FileSystemFunctions: FileDateTime(), FileLen(), GetAttr(),
@@ -33,7 +37,7 @@
 - Design full, detailed timetable.
 - Consider marketing strategy.
 - Write the !@#$ing thing.
-- Slow down a bit so Greg can catch up.
+- Slow down a bit so Greg can catch up. :)
 - ...and much, much more.
 
 

diff --git a/docs/windows_compatibility.txt b/docs/windows_compatibility.txt
@@ -4,7 +4,7 @@ Some notes on platform-independence and Windows:
    different design concepts, and partially through design flaws) with
    Unix.
 
-  Secondly, Unix is very different from, say, a Macintosh.
+  Secondly, Unix is very different from, say, MacOS.
 
   Visual BASIC is written specifically for Windows; you can see this in
    its API.