foretspaisibles / gasoline Goto Github PK

As we have an opam port, it would be even more useful if it supports pinning.

We need to provide a real META file.

This should improve compatibility with opam.

Formatting indications should be optional.

This should be an example of our Unicode facility and application patterns.

Reference:

• https://linuxfr.org/users/elessar/journaux/esod-mumixam

An application should be able to fingerprint itself — e.g. for a bug report. A complete fingerprint should mention the list of its components together with their versions.

The getopt prefix used by components to register long options does not work in v0.1. For instance the wordgen example fails when it is invoked as follows:

% ./wordgen -A number=5
wordgen: illegal option -- A
Usage: wordgen [-h]
Exit 64

It is instead expected that -A number=5 sets the configuration parameter Wordgen.Component_automaton.Configuration.generate_n to the value 5.

We want to implement a very high-level reusable component facility which allows to quickly combine high-level operations much like the Unix shell or Apple Automator do.

Write a command wrapper pattern, for tools similar to OCamlfind.

Implement a standard component initialising the random numbers facility found in the standard library.

Software component functionalities should run in an execution monad. These functionalities are not allowed to throw exceptions and report errors in the monad.

Implement a component initialising the “Graphics” library.

• Documentation must use “Unixish” instead of other C-ish expressions.
• Modules should be renamed to “Unixish_” instead of “C_”.

We should add a Lwt backed diagnostic facility.

Once foretspaisibles/bsdowl#119 has been fixed, we do not need to set the value of LIBDIR ourselves.

The operation make distclean should remove unit testing logfiles from the source directory.