Front Page All Articles Recent Changes Random Article

Contents

Concatenative language

  • ACL
  • Ait
  • Aocla
  • Breeze
  • Cat
  • Cognate
  • colorForth
  • CoSy
  • Deque
  • Elymas
  • Enchilada
  • ETAC
  • F
  • Factor
  • Forth
  • Freelang
  • Gershwin
  • Joy
  • Kitten
  • lang5
  • Lviv
  • min
  • mjoy
  • Mlatu
  • Ode
  • Om
  • Onyx
  • Plorth
  • Popr
  • Porth
  • PostScript
  • Quackery
  • r3
  • Raven
  • Retro
  • Staapl
  • Stabel
  • Trith
  • Worst
  • xs
  • XY
  • 5th
  • 8th

Other languages

  • APL
  • C++
  • Erlang
  • FP trivia
  • Haskell
  • Io
  • Java
  • JavaScript
  • Lisp
  • ML
  • Oberon
  • RPL
  • Self
  • Slate
  • Smalltalk

Computer Science

  • Type systems
  • Language paradigms
  • Compilers
  • Interpreters
  • Garbage collection

Meta

  • Search
  • Farkup wiki format
  • People
  • Etiquette
  • Sandbox

Factor/Goals

The goals of the Factor project are to build a Concatenative language and Interactive environment suitable for the development of large-scale applications. Specifically,

  • Factor should support powerful, orthogonal and well-designed Language features. Boilerplate should not be tolerated.
  • Factor should be fast, without requiring undue effort on the part of the developer. As much as possible, the compiler should infer the developer's intent and make common idioms fast; type hints should be supported but only relied upon as a matter of last resort. Using Unsafe words should never be a requirement for achieving high performance. See Factor compiler.
  • Factor should be robust. Unit testing, Continuous integration and Static analysis should be employed as much as possible to ensure the robustness of the implementation.
  • Software written in Factor should be robust. Factor avoid language features which encourage Fragile code, and the language should make it easy to achieve Code reuse and Encapsulation.
  • Factor should have a large set of libraries for common programming tasks, such as parsing XML, writing web applications, 2D and 3D graphics, database access, sockets, and so on. These libraries should be well-tested, well-documented and ship with Factor.
  • Factor should include powerful developer tools to automate some of the drudgery in maintaining larger code bases.
  • Factor should include top-notch documentation, accessible from within the development environment itself, to aid beginners and experts like. See Help system.

This revision created on Tue, 9 Sep 2008 03:03:47 by slava

Latest Revisions Edit

All content is © 2008-2023 by its respective authors. By adding content to this wiki, you agree to release it under the BSD license.