XULRunner42 edited this page Sep 14, 2010 · 3 revisions
Clone this wiki locally

Welcome to the ferite-20094 wiki!

Hope that you will enjoy working with ferite language and may this guide be a help to you.

  • Why are you doing this?

The ferite language has never been fully appreciated. Just kidding. I actually don’t know anything about the history of ferite, though it appears to be a mature and a really used programming language, there doesn’t seem to be much of a fan club. Boris (ctr, the author) said I could “corner him” and have an opportunity to ask some questions later this week.

  • Is ferite a dead language?

The last big public news for Ferite seems to have been in 2005, and the 1.1 release series that has generated some more recent footnotes on the SourceForge page for ferite is shrouded in darkness. Not really… only that the website seems to still indicate that 1.1 series is not out yet, or not ready for production. Ferite is no more dead than C, and the ferite engine provides some tools that do not otherwise “come with” C, while spending a great deal of effort on protocols to manage “interfacing” with C code.

So, while there is usually not anybody in #ferite/irc.freenode.net, the language is alive and well for your rapid prototyping needs.

  • Is ferite a compiled language?

Ferite code is made up of scripts that you run directly with an interpreter. Ferite is also a modular language. These modules can be compiled (C code must be compiled to be executed.) I am not clear about the difference between native modules and hybrid modules, but the interesting bit is that you find C code wrapped in ferite code, and it is somehow incorporated into your program. This paper is supposed to explain how C and ferite are integrated with .fec files: Extending and Embedding The Ferite Engine