summaryrefslogtreecommitdiff
path: root/content/gemtext/gemfeed/2010-05-09-the-fype-programming-language.gmi
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-21 05:11:04 +0100
commitdcd442adbac004e4974932ac7f39117f9e259865 (patch)
tree369399aee977965eb3c935a01baf7b5cbb37c8be /content/gemtext/gemfeed/2010-05-09-the-fype-programming-language.gmi
parentbe8db9d60b582fc5afa387533909b5d364739512 (diff)
separate header from impl.
Diffstat (limited to 'content/gemtext/gemfeed/2010-05-09-the-fype-programming-language.gmi')
-rw-r--r--content/gemtext/gemfeed/2010-05-09-the-fype-programming-language.gmi4
1 files changed, 3 insertions, 1 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() {