|
|
At the very low level, and only when needed, Phix has all the tools required (about a dozen) to
allocate some memory, set the appropriate bits and bytes, invoke operating system or third party
routines (in a dll/so, typically written in C), and finally (you can automate this) release memory
for reuse. It is also possible to do all that directly with inline assembly (which most users should
quite rightly avoid). Such code (eg builtins\VM or demo\pGUI) is normally written once and used in
several different projects.
However, for day-to-day use at the normal high/human-readable level, in Phix you just use the
five simple types listed above. It is entirely expected that anyone who has experience of more
"advanced" languages might blurt out "ridiculous" or something similar or cruder at this point.
However, the Phix compiler/interpreter, which can re-compile itself (four times) in just 6 seconds,
the Edita programmers editor, all the demonstration programs included in the package, and indeed
the program used to generate this very help file (docs\phix\makephix.exw), use nothing else, and
are testament to the fact that the above five simple types are more than perfectly adequate.
The type "number" (introduced in 0.8.3) is a simple alias of "atom" (the legacy name for that type).
The rest of these docs and all examples use "atom" for legacy reasons and compatibility with Euphoria.
There is deliberately no separate "float" type, rather 1.0 is stored as the integer 1, and that
can be used in floating point calculations without any casting or other type coercion.
Technically there is such a thing internally, T_N, which is "fraction but not whole number",
however were that exposed it would simply break should some result happen to be a whole integer,
such as 1.5+1.5, so T_N is only ever used for fixed fractional constant values, or values exceeding
the capacity of an integer, that are known at compile-time.
You could theoretically write an entire application declaring all variables and parameters as type object,
except that it would probably not catch errors the way you might expect it to. While Phix does also allow
user defined types to be declared, they are used primarily for validation
and debugging purposes, rather than being fundamentally different to the above.
For comparison, I stumbled on this in a Ruby pdf
+------------------+
| |
Object---->(Object) |
^ ^ ^ ^ |
| | | | |
| | +-----+ +---------+ |
| | | | |
| +-----------+ | |
| | | | |
+------+ | Module--->(Module) |
| | ^ ^ |
OtherClass-->(OtherClass) | | |
| | |
Class---->(Class) |
^ |
| |
+----------------+
with a
link
to an updated version:
+----------+ +-...
| | |
BasicObject-----|--->(BasicObject)-------|-...
^ | ^ |
| | | |
Object---------|------>(Object)---------|-...
^ | ^ |
| | | |
+-------+ | +--------+ |
| | | | | |
| Module-|----------|--->(Module)-|-...
| ^ | | ^ |
| | | | | |
| Class-|----------|---->(Class)-|-...
| ^ | | ^ |
| +---+ | +----+
| |
obj--->OtherClass------------>(OtherClass)----------...
neither of which make the slightest bit of sense to me...
|
