Reimplement most of the object system to align with AMOP.

Signed-off-by: Amy Ringo <me@remexre.com>

Author: remexre

doc/z/z-for-lispers.md

@@ -4,8 +4,13 @@ Z started life as a "modernized" Common Lisp variant, so lots of parts of it wil
 Some notable Common Lisp-specific things are mentioned here.
 
 - An [iterate](https://iterate.common-lisp.dev/)-like loop syntax is present instead of a `CL:LOOP`-like one.
-- The equivalent of a CL package is a Z module.
-  The equivalent of a CL system is a Z package.
+- Many names are "modernized" to be more familiar to non-CL programmers.
+  A few instances of this that might otherwise be confusing:
+  - The equivalent of a CL package is a Z module.
+  - The equivalent of a CL system is a Z package.
 - Most modules are loaded from files with a scheme similar to `package-inferred-system`.
 - [Package-local nicknames](https://gist.github.com/phoe/2b63f33a2a4727a437403eceb7a6b4a3) are supported.
 - Most polymorphic functions are generic functions, similar to what [GENERIC-CL](https://gutev.dev/generic-cl/) does.
+- Z tracks dependencies between functions, so callers automatically get recompiled when an `INLINE` function is redefined.
+- Z's compiler has a more sophisticated inliner than most CL implementations, so `INLINE` is applied to function definitions by default.
+  - There is a `MUST-INLINE` declaration to override the inliner's decisions.

src/zpy/main.py

@@ -6,13 +6,14 @@
 
 from pathlib import Path
 from sys import argv
-from zval import ModuleZ
+from zval import Z
 
 
 def main(src_path: Path, *args: str):
     with src_path.open() as src_file:
         src = src_file.read()
 
+    print(Z["MAKE-INSTANCE"].call(Z["STANDARD-OBJECT"]))
     pass