From 368c4a541fb1f989c6644116dd3ad1d383893c31 Mon Sep 17 00:00:00 2001
From: captainurist <73941350+captainurist@users.noreply.github.com>
Date: Sun, 5 Nov 2023 19:30:34 +0000
Subject: [PATCH] Update HACKING

---
 HACKING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/HACKING.md b/HACKING.md
index c32f1fd3d21b..e79f4a2f86de 100644
--- a/HACKING.md
+++ b/HACKING.md
@@ -122,8 +122,8 @@ Code Organization
 OpenEnroth code is broken up as follows:
 * `thirdparty` – this is where all external libraries go.
 * `Utility` – generic utility classes and functions go here. Utility classes should be domain-independent (e.g. should make sense in a context of some other project) and should depend only on `thirdparty` libraries.
-* `Platform` – our platform abstraction layer on top of SDL. Platform classes should also be reasonably domain-independent and should depend only on `Utility`.
-* `Library` – collection of independent libraries that the engine is built on top of. Code here can depend on `Utility`, `Platform`, and other libraries in `Library`.
+* `Library` – collection of independent libraries that the engine is built on top of. Code here can depend on `Utility` and other libraries in `Library`. However, there should be no cyclical dependencies between libraries here.
+* `Library/Platform` is our platform abstraction layer on top of SDL.
 * The rest of the code is currently pretty tangled with each part depending on each other. This document will be updated once we have some progress there.
 
 Our basic guidelines for code organization are: