Update README.md

README.md

@@ -4,27 +4,47 @@ A simple, powerful lua console with the intent of replacing CMD and Terminal + L
 
 ### TODO
 * Move additions to separate global table 'add'
-* Triple check buffer overflows and mem alignment and memleaks
-* Add `-l string` option to allow dll's to be loaded easier
+* Triple check buffer overflows and mem alignment and memleaks, as well as iffy -1 versus 1 when using lua_*
 
 # About
-
-Lua Console | Version: 9/26/2017
+luaw -?  
+```
+Lua Console | Version: 12/31/2017
 Lua 5.3.4  Copyright (C) 1994-2017 Lua.org, PUC-Rio
 LuaConsole Copyright MIT (C) 2017 Hydroque
 
-- Line by Line interpretation
-- Files executed by passing argument
-- Working directory support addition
-- Built in stack-dump addition
-- Console clear addition
-- Supports Lua5.3, Lua5.2, Lua5.1
+Supports Lua5.3, Lua5.2, Lua5.1
+5.2.x and 5.1.x assume that you have enough memory for initial functions.
+
+        - Line by Line interpretation
+        - Files executed by passing
+        - Global variable defintions
+        - Dynamic module loading
+        - Working directory support
+        - Built in stack-dump
+        - Console clearing
+
+Usage: lua.exe [FILE_PATH] [-v] [-e] [-s START_PATH] [-p] [-a] [-c] [-Dvar=val]
+[-Lfilepath.lua] [-b] [-?] [-n]{parameter1 ...}
+
+-v       Prints the Lua version in use
+-e       Prevents lua core libraries from loading
+-s       Issues a new root path
+-p       Has console post exist after script in line by line mode
+-a       Disables the additions
+-c       No copyright on init
+-d       Defines a global variable as value after '='
+-l       Executes a module before specified script or post-exist
+-b       Load specified parameters by -n before -l modules execute
+-n       Start of parameter section
+-?       Displays this help message
+```
 
-A console whose code is much easier to look at and handle than the one provided native with Lua. Supports everything Lua's console does except multiline support. Runs compiled source without a problem. Use -? to get a list of the switches. Should work on linux as well as mac and windows. If it doesn't make a pull request and/or start an issue.
+A console whose code is much easier to look at and handle than the one provided native with Lua. Has more functionality with native lua console. Supports everything Lua's console does except multiline support in-post-exist. Runs compiled source without a problem. Use -? to get a list of the switches above (different depending on how you build it). Works on Linux, Windows, and Mac. Support for LuaRocks is in the wiki. Want to contribute? Submit a pull request. Want to report a bug? Start an issue. Ideas? Start an issue.
 
 # Additions
 
-There is an 'additions' module to this interpretor, which is completely up to the user to utilize. You can temporarily disable them with the -a switch, or even keep them out of your build. Doing so will take away the added `os.getcwd()` and `os.setcwd(string)` and `stackdump(...)` and `os.clear()` functions, which let you set the current working directory and view your stack. A clear function also has been added, which should uses the nasty system() call as well as use clear (cls only on windows). Lua Console acts much like a console now that the additions were added. 
+There is an 'additions' module to this interpreter, which is completely up to the user to utilize. You can temporarily disable them with the -a switch, or even keep them out of your build. Doing so will take away the added `os.getcwd()` and `os.setcwd(string)` and `stackdump(...)` and `os.clear()` functions, which let you set the current working directory and view your stack. A clear function also has been added, which uses the nasty system() call as well as use clear (cls only on windows). Lua Console acts much like a console now that the additions were added. 
 
 stackdump() is a global function. It works as easy as print does, but it does type conversion from lua to C-string and lists anything left in the stack.
 
@@ -39,7 +59,6 @@ For example, <br>
 
 This sure beats `print(type(data), data)` calls, and can be used to detect anything left on the stack in C. To add your own C functions, inherit the project and modify the additions.c file only. Another method to adding C functions is creating a similar dll file:
 ```
-
 #include <stdio.h>
 #include "lua.h"
 
@@ -52,7 +71,7 @@ LUA_DLL_EXPORT luaopen_testdll(lua_State *L) {
 	return 0;
 }
 ```
-This is how LuaRocks does it, but they have file formats and containers. Everything LuaRocks compiles down to a dll or two, gets loaded, then taken over by whatever lua script loaded it. Then just compile and run load it in lua:
+This is how LuaRocks does it, but they have file formats and containers. Everything LuaRocks compiles down to a dll or two, gets loaded, then taken over by whatever lua script loaded it. Then just compile and run it in lua:
 ```
 gcc -g0 -O2 -Wall -c testdll.c
 gcc -g0 -O2 -Wall -shared -o testdll.dll testdll.o
@@ -63,11 +82,11 @@ print(testdll) -> function
 testdll()  -> Loaded successfully!
 ```
 
-Added very comprehensive error feedback, which tells you about the stack (stack dumps, too, if not just the error is on the stack), the type of error (syntax/runtime), and the regular lua feedback string with the line number sammich'd between two colons.
+Added very comprehensive error feedback, which tells you about the stack (stack dumps, too, if not just the error is on the stack), the type of error (syntax/runtime), and the regular lua feedback string with the line number sammich'd between two colons. Now with file name!
 
 For example, <br>
 >\>. <br>
->(Syntax) | Stack Top: 1 | [string "."]:1: unexpected symbol near '.' <br>
+>(Syntax) | Stack Top: 1 | Example_Error.lua | [string "."]:1: unexpected symbol near '.' <br>
 
 # Using with LuaRocks
 [Windows MinGW](https://github.com/Hydroque/LuaConsole/wiki/LuaRocks-Support-Windows-MinGW)