summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Buetow <git@mx.buetow.org>2021-05-05 09:38:11 +0100
committerPaul Buetow <git@mx.buetow.org>2021-05-05 09:38:11 +0100
commitabf8a0771b912c5e19368a913827932bc3bd9a21 (patch)
treec5975e774441a5644fe607963d2991b9754d1ae3
parent721f56d3cc981e3424a595bcb78d231ce5f4bdb3 (diff)
separate header from impl.
-rw-r--r--content/gemtext/gemfeed/2010-05-09-the-fype-programming-language.gmi4
-rw-r--r--content/html/gemfeed/2010-05-09-the-fype-programming-language.html3
2 files changed, 5 insertions, 2 deletions
diff --git a/content/gemtext/gemfeed/2010-05-09-the-fype-programming-language.gmi b/content/gemtext/gemfeed/2010-05-09-the-fype-programming-language.gmi
index 064a08ce..ac7c3790 100644
--- a/content/gemtext/gemfeed/2010-05-09-the-fype-programming-language.gmi
+++ b/content/gemtext/gemfeed/2010-05-09-the-fype-programming-language.gmi
@@ -24,7 +24,7 @@ Fype is a recursive acronym and means "Fype is For Your Program Execution" or "F
The Fype interpreter is written in an object oriented style of C. Each "main component" has its own .h and .c file. There is a struct type for each (most components at least) component which can be initialized using a "COMPONENT_new" function and destroyed using a "COMPONENT_delete" function. Method calls follow the same schema, e.g. "COMPONENT_METHODNAME". There is no such as class inheritance and polymorphism involved.
-To give you an idea how it works here as an example is a snippet from the main Fype "class":
+To give you an idea how it works here as an example is a snippet from the main Fype "class header":
```
typedef struct {
@@ -35,6 +35,8 @@ typedef struct {
} Fype;
```
+And here is a snippet from the main Fype "class implementation":
+
```
Fype*
fype_new() {
diff --git a/content/html/gemfeed/2010-05-09-the-fype-programming-language.html b/content/html/gemfeed/2010-05-09-the-fype-programming-language.html
index 41bfc0e7..40beea42 100644
--- a/content/html/gemfeed/2010-05-09-the-fype-programming-language.html
+++ b/content/html/gemfeed/2010-05-09-the-fype-programming-language.html
@@ -35,7 +35,7 @@ li { color: #98be65; }
<p>Fype is a recursive acronym and means "Fype is For Your Program Execution" or "Fype is Free Yak Programmed for ELF". You could also say "It's not a hype - it's Fype!".</p>
<h2>Object oriented C style</h2>
<p>The Fype interpreter is written in an object oriented style of C. Each "main component" has its own .h and .c file. There is a struct type for each (most components at least) component which can be initialized using a "COMPONENT_new" function and destroyed using a "COMPONENT_delete" function. Method calls follow the same schema, e.g. "COMPONENT_METHODNAME". There is no such as class inheritance and polymorphism involved. </p>
-<p>To give you an idea how it works here as an example is a snippet from the main Fype "class":</p>
+<p>To give you an idea how it works here as an example is a snippet from the main Fype "class header":</p>
<pre>
typedef struct {
Tupel *p_tupel_argv; // Contains command line options
@@ -44,6 +44,7 @@ typedef struct {
char *c_basename;
} Fype;
</pre>
+<p>And here is a snippet from the main Fype "class implementation":</p>
<pre>
Fype*
fype_new() {