moa/emulator/core/Cargo.toml

[package]
name = "moa-core"
version = "0.1.0"
edition = "2021"

[dependencies]
log = "0.4"
femtos = "0.1"
thiserror = "1.0"
moa-host = { path = "../libraries/host" }
emulator-hal = { path = "/media/work/projects/emulator-hal/emulator-hal" }
Major reorganization into crates I wanted to make this a bit more modular, so it's easier in theory to write external crates that can reuse bits, and selectively compile in bits, such as adding new systems or new cpu implementations 2022-09-25 06:14:03 +00:00			`[package]`
Renamed modules to use kebab case 2024-02-25 03:26:28 +00:00			`name = "moa-core"`
Major reorganization into crates I wanted to make this a bit more modular, so it's easier in theory to write external crates that can reuse bits, and selectively compile in bits, such as adding new systems or new cpu implementations 2022-09-25 06:14:03 +00:00			`version = "0.1.0"`
			`edition = "2021"`

			`[dependencies]`
Added log crate 2022-10-09 16:40:20 +00:00			`log = "0.4"`
Modified to use crates.io version of femtos 2024-02-25 03:16:46 +00:00			`femtos = "0.1"`
Split some parts of moa-core into libraries/ 2024-03-02 05:17:09 +00:00			`thiserror = "1.0"`
			`moa-host = { path = "../libraries/host" }`
Refactoring m68k to use a temporary cycle struct I'm trying to extract the memory/bus interface, and pass it in at the start of each cycle instead of having the BusPort permanently embedded, which will allow migrating to emulator-hal. The functional way would be argument drilling; passing an extra argument to each function in the entire execution core. The problem is that it's messy, so a solution that is still functional is to implement all of the execution logic on a newtype that contains a reference to the mutable state and the owned cycle data, and at the end of the cycle, decompose the M68kCycleGuard that holds the reference, and keep the cycle data for debugging purposes. 2024-03-03 07:48:19 +00:00			`emulator-hal = { path = "/media/work/projects/emulator-hal/emulator-hal" }`