Releases: AlchemicRaker/OpenProlog
Crashes and Computers
Added computer/2
for exploring some computer properties. Also fixed a crashing regression, where error messages were not being sent to OC correctly (so, now they can be analyzed again, and display on the screen).
Maps and Navigation
v0.3.6 Version 0.3.6
Signals and Sleep improvements, jiprolog cleanup
v0.3.5 Version 0.3.5
Exception Catching and Friendly Machines update
Lots of new exception catching, error message routing, and prolog engine-stopping code has been added. Machine.pl also no longer requires gpu & screen to exist, so drones can be coded.
Machine.pl will still bind the first gpu it identifies to the first screen it identifies, if they exist, which is behavior that should probably be removed later.
String Formatting Fix
v0.3.3 Version 0.3.3
Memory Leak Patch
v0.3.2 Version 0.3.2
Playable Development Release, Stability Update
Catch startup errors and some other error cases.
Playable Development Release
Functional enough for a Prolog Architecture to boot (consult) from EEPROM, and for that BIOS to further boot (consult) from attached filesystems.
The provided Prolog EEPROM contains some sample debug code for loading from filesystems and observing signals. You may write init.pl
files onto a filesystem to have the rules automatically loaded. initest/1
will be queried after loading init.pl
, and may be used to run a program. Alternatively, writing rules to on_signal/1
will let you run those queries as those signals are received by the bios.