From dcd442adbac004e4974932ac7f39117f9e259865 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 5 May 2021 09:38:11 +0100 Subject: separate header from impl. --- content/html/gemfeed/2010-05-09-the-fype-programming-language.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'content/html/gemfeed') 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; }

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!".

Object oriented C style

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 {
    Tupel *p_tupel_argv; // Contains command line options
@@ -44,6 +44,7 @@ typedef struct {
    char *c_basename;
 } Fype;
+

And here is a snippet from the main Fype "class implementation":

 Fype*
 fype_new() {
-- 
cgit v1.2.3