Fix a few typos, start draft of fn-star-talkin-bout-my-generation

Author: dmiller

_drafts/2025-09-07-fn-star-talkin-bout-my-generation.md

@@ -0,0 +1,38 @@
+---
+layout: post
+title: C4 - fn*: talkin' 'bout my generation
+date: 2025-09-07 00:00:00 -0500
+categories: general
+---
+
+We look at code generation for functions in ClojureCLR.
+
+In a previous post ([C4: Functional anatomy]({{site.baseurl}}{% post_url 2025-09-04-functional-anatomy %})), we looked at how functions are represented in ClojureCLR.  That post focused on the interfaces and classes that form the basis of the representation of functions.  When we generate a function in ClojureCLR, though we are deriving a class from one of the base classes (typically `AFunction` or `RestFn`), there is a significant amount of support structure that gets added.  That is the topic of this post.
+
+## Our playground
+
+The primary classes involved in function code generation are:
+
+<img src="{{site.baseurl | prepend: site.url}}/assets/images/objexpr.png" alt="Graph of all types related to ObjExpr" />
+
+I have no idea why `ObjExpr` and `ObjMethod` are named what they are.
+`FnExpr` is the AST node that represents an `fn*` form.  `FnMethod` represents an `invoke` method of the generated class. 
+`NewInstanceExpr` represents a `deftype` or `reify` form; `NewInstanceMethod` represents a method of the generated class.
+For these, a significant amount of code lies in the base classes `ObjExpr` and `ObjMethod`. We will focus here on `FnExpr` and `FnMethod`.  Most of this analysis applies to `NewInstanceExpr` and `NewInstanceMethod` as well.
+
+Note: Do not confuse `NewInstanceExpr` with `NewExpr` -- the latter represents a `new` form that creates an instance of a class.
+
+## Let me count the lines
+
+| File | Source lines | Executable lines |
+|------|--------------:|------------------:|
+| ObjExpr.cs |  1,195 | 450 |
+| FnExpr.cs  |  362 |  102 |
+| NewInstanceExpr.cs |  681 | 227 |
+| ObjMethod.cs |  176 |  50 | 
+| FnMethod.cs  |  458 |  157 | 
+| NewInstanceMethod.cs |  321 |  117 |
+
+Doesn't seem like much?  It's packed.  And dependent on a some other goodies that we will get to shortly.
+
+##

_posts/2025-08-31-classic-clojure-compiler-contemplation.md

@@ -14,11 +14,12 @@ The other posts in the series are:
 - [C4: Symbolic of what?]({{site.baseurl}}{% post_url 2025-09-02-symbolic-of-what %}) - A little digression on what symbols represent
 - [C4: ISeq clarity]({{site.baseurl}}{% post_url 2025-09-03-iseq-clarity %}) - How to analyze an `ISeq`
 - [C4: Functional anatomy]({{site.baseurl}}{% post_url 2025-09-04-functional-anatomy %}) - How functions are implemented in Clojure
-- __C4: The fn*: talkin' 'bout my generation__ - Code-gen for functions
+- __C4: fn*: talkin' 'bout my generation__ - Code-gen for functions
 - __C4: How type-ical__ - Type analysis by the compiler
 - __C4: I have something to emit__ - More on code generation
 - __C4: A time for reflection__ -- Reflection and dynamic callsites
 - __C4: Is there a protocol for that?__ -- Protocols
+- __C4: Out of control__ -- Some points about flow of control and data in the compiler
 
 ## The terms of discussion
 

_posts/2025-09-04-functional-anatomy.md

@@ -5,7 +5,7 @@ date: 2025-09-04 00:00:00 -0500
 categories: general
 ---
 
-We look at the implementation of functions in ClojureCLR and how evaluation/compilation translates a source code definition of a function to the underlying class representation.
+We look at the implementation of functions in ClojureCLR and how evaluation/compilation translates a source code definition of a function to the underlying class representation.  (The first of several posts on this topic.)
 
 ## The universe, and everything
 

assets/images/objexpr.png

@@ -0,0 +1,26 @@
+strict digraph G {
+
+rankdir = RL;
+
+node [shape=box];
+	
+subgraph objexprrelated {
+	node [shape=box];
+
+    Expr;
+	ObjExpr -> { Expr };
+    NewInstanceExpr -> { ObjExpr };
+    FnExpr -> { ObjExpr };
+
+}	
+
+subgraph objmethodrelated {
+	node [shape=box];
+
+	ObjMethod;
+    NewInstanceMethod -> { ObjMethod };
+    FnMethod -> { ObjMethod };
+}	
+
+
+}