argv exec

Author: rumbledethumps

docs/source/os.rst

@@ -489,6 +489,48 @@ ERRNO_OPT
         - 85
         -
 
+ARGV
+----
+
+.. c:function:: int _argv (char *argv, int size)
+
+   |
+
+   The virtual _argv is called by C initialization to provide argc and argv for main().
+   It returns an array of zero terminated string indexes followed by the strings.
+   e.g. ["ABC", "DEF"] is 06 00 0A 00 00 00 41 42 43 00 44 45 46 00
+   The returned data is guaranteed to be valid.
+
+   :Op code: RIA_OP_ARGV 0x08
+   :C proto: (none)
+   :returns: Size of argv data
+   :errno: will not fail
+
+EXEC
+----
+
+.. c:function:: int ria_execl (const char *path, ...)
+.. c:function:: int ria_execv (const char *path, char * const argv[])
+.. c:function:: int _exec (const char *argv, int size)
+
+   |
+
+   The virtual _exec is called by ria_execl() and ria_execv(). Be aware of the
+   one difference from the execl() and execv() you may be used to. Because RAM
+   is precious, the path is only supplied once, not again in argv[0]. The
+   launched ROM will see argv[0] as the filename.
+
+   The data sent by _exec() will be checked for pointer safety and sanity, but
+   will assume the path points to a loadable ROM file. If API_EINVAL is returned,
+   the argv buffer is cleared so further attempts to _argv() will return an empty set.
+   Is the ROM is invalid, the user will be left on the console with an error message.
+
+   :Op code: RIA_OP_ARGV 0x09
+   :C proto: rp6502.h
+   :returns: Size of argv data
+   :errno: API_EINVAL
+
+
 CLOCK
 -----
 
@@ -533,7 +575,7 @@ TZSET
 -----
 
 .. c:function:: int void tzset(void);
-.. c:function:: int f_tzset (struct _tzset *tz)
+.. c:function:: int _tzset (struct _tzset *tz)
 
    .. code-block:: c
 
@@ -545,8 +587,8 @@ TZSET
          char dstname[5];  /* Name when daylight true, e.g. CEST */
       };
 
-   The virtual f_tzset() is the how tzset() is implemented. Use `help set tz` on the
-   monitor to learn about configuring your time zone.
+   The virtual _tzset() is called internally by tzset(). Use `help set tz` on the
+   console monitor to learn about configuring your time zone.
 
    :Op code: RIA_OP_TZSET 0x0D
    :C proto: time.h
@@ -558,7 +600,7 @@ TZQUERY
 -------
 
 .. c:function:: struct tm *localtime(const time_t *timep);
-.. c:function:: int f_tzquery (uint32_t time, struct _tzquery *dst)
+.. c:function:: int _tzquery (uint32_t time, struct _tzquery *dst)
 
    .. code-block:: c
 
@@ -567,7 +609,7 @@ TZQUERY
          int8_t daylight;  /* non 0 if daylight savings time active */
       };
 
-   The virtual f_tzquery() is part of how localtime() is implemented.
+   The virtual _tzquery() is called internally by localtime().
 
    :Op code: RIA_OP_TZQUERY 0x0E
    :C proto: time.h

docs/source/ria.rst

@@ -693,21 +693,22 @@ Console Port
 The main serial port of the RIA is the console for system. Modern operating
 systems provide canonical input and translated output via a configurable
 layer such as termios. A full termios is a too heavy for an 8-bit system,
-but raw and non-blocking IO options are also provided.
+but raw and non-blocking IO options need to be provided.
 
 The well known stdin blocks for canonical input. The console user will be
 prompted to edit a line. Once the line is submitted with the enter key,
 the stdin read unblocks and returns the line up to a linefeed character.
 
 The well known stdout and stderr blocks and inserts carriage returns
-before newlines is one is not present. The full amount of data is always
+before newlines if one is not present. The full amount of data is always
 sent and writes will block until sent data is fully unloaded into hardware
 FIFOs.
 
-This is what a C programmer expects, but is not a good interface for a
-multitasking 6502 OS to use. To that end, a non-blocking interface to the
-console is provided. Simply open the special filename "CON:". Reads can
-return 0 bytes, and writes may send less than the requested amount.
+These well know console interfaces are what a C programmer expects, but it is
+not a good interface for a multitasking 6502 OS to use. To that end, a
+non-blocking interface to the console is provided. Simply open the special
+filename "CON:". Reads can return 0 bytes, and writes may send less than the
+requested amount.
 
 Going one step further, a non-blocking and raw connection to the console
 port is available on special filename "TTY:". There is no canonical input