more field logic

doc/logbooks/000-Main-Logbook

@@ -32,15 +32,14 @@ Basically, i'd define a ton of helper functions that return the signal identifie
 Dev Todo list
 ================================================================================
 
-- tidy up stuff
-    - merge FieldBuilder and FieldLogic classes. It makes no sense for these to be separate
-    - propagate the exporter class EVERYWHERE
-      shorten it to simply "self.exp"
-- Build out a few more NextStateConditional implementations
-    - hw we
+- Link more functions to the dereferencer
+    I shouldn't have to go to the hwif or whatever
+    dereferencer should have all the query functions
 
 - readback mux
 
+- Other field output assignments
+
 - HWIF layer
     - User Signals
         Generate these in the io struct? I forget what I decided

doc/logbooks/Validation Needed

@@ -82,7 +82,19 @@ X If a node ispresent=true, and any of it's properties are a reference,
     then those references' ispresent shall also be true
     This is an explicit clause in the spec: 5.3.1-i
 
+! Flag illegal sw actions if not readable/writable
+    The following combinations dont get flagged currently:
+        sw=w; rclr;
+        sw=w; rset;
+        sw=r; woset;
+        sw=r; woclr;
+    their counterparts do get flagged. such as:
+        sw=w; onread=rclr;
 
+! hwclr/hwset/we/wel probably shouldn't be able to reference itself
+    y->hwclr = y;
+    y->we = y;
+    ... it works, but should it be allowed? Seems like user-error
 
 
 

doc/logbooks/template-layers/4-fields

@@ -74,7 +74,7 @@ NextStateConditional Class
         it instructs the FieldBuider that code for this conditional shall be emitted
         TODO: better name than "is_match"? More like "is this relevant"
 
-    - get_conditional(self, field: FieldNode) -> str:
+    - get_predicate(self, field: FieldNode) -> str:
         Returns the rendered conditional text
 
     - get_assignments(self, field: FieldNode) -> List[str]: