The purpose is to get quickly a clear error message about the version of the compiler, rather than a strange error message caused by an update in the compiler and/or in the stdlib. It is recommended to use this option in your Makefile for applications using new features, or new functions of the stdlib, or in any application published somewhere, and potentially compiled by people having wild and heterogeneous versions of Opa (nightly builds, from sources).
…heduler * This is a tmp fix, the problem needs to be solved with a deeper investigation about non-cps second order bypass projections (in progress)
This commit is orthogonal with the question about scheduling re-entrance, which will be treated in the next commit.
… of the now dead file
deprecated or resolved or present in dead code
* Jscompiler takes now env_typer + code instead of old blender type * flattening env_blender in qmlcompilers (qmljs command line tool) * inline the part about typing from the blender in qmlcompilers The blender was still used only by qmljs which does not support db constructions (used only for debug and tests of pure client code) so it does not need to treat db constructions anymore.
Since qmlflat calls now opa (cf generated script qmlflat), qmlcompilers is only used by the command line tool qmljs. db constructions are not handled by qmljs (only client code tests) Opa uses others passes for treating the db nodes, so the code about db stuff in the blender is never executed.
Now it (again) passes all unit testing.
on some forall
in trx_ocaml & trx_interpreter