Recurring questions and related answers. If you have a question that isn't answered below, please feel free to search for or post it to one of the mailing lists or forums listed on the contacts page.

Currently, there is no release date set. Work continues at a casual pace. All development milestones are not strict and may slip as needed. Currently, planned public release will begin at beta (possibly alpha).

In short, it'll be done when it's done.

There is not really any concrete reason for the name. It needed to be unique and identifable but beyond that, no restrictions.

After considering several names, "Redtail" just sort of stuck.

A scripting engine is basically a modular component that applications can embed to offload program logic into easy-to-modify script files. Applications that embed a scripting engine can load and execute code on the fly without compilation. This results in very flexible applications.

At its simplest, a script engine can provide configuration-file-like capability. At the other end of the spectrum, the application itself can merely be an interface to the operating system and all program logic can be performed by the scripts.

Most currently available scripting engines use a procedural language for their scripts (see Lua). As a functional, Scheme-like language, Redtail script provides a different approach. It remains just as powerful but allows users to apply functional programming techniques in problem solving.

Currently, Redtail is a one-man project conceived, planned, and written by jduclos as a personal hobby. However, if you feel you have a compelling argument for your inclusion, please contact the Redtail project.

The best way to help is simply to use Redtail and submit any bugs found. Extra sets of eyes are always appreciated.

There are no plans to accept donations to the Redtail project at this or any future time.