Kay Gürtzig

There is a rudimentary Haxe grammar for [GOLDparser](http://www.goldparser.org/) in the net (see [https://haxe.motion-twin.narkive.com/xeAmBeFG/full-grammar](https://haxe.motion-twin.narkive.com/xeAmBeFG/full-grammar), [http://www.semitwist.com/download/haxepred/Haxe_gold_0.2.zip](http://www.semitwist.com/download/haxepred/Haxe_gold_0.2.zip)) that could be used as starting point for Haxe code import, together with some preprocessing efforts...

Partially fixed (for the explicit use of div operators).

Will be accomplished together with #800.

I'm not quite convinced of the shipping of sample files with the "binary" distribution (tends to blow up the download with more or less redundant stuff). I think for the...

@GitMensch > Adding the samples and expected results is in any case a useful thing (actually should seen as pre-requisite) for automated testing brought up in the past more than...

As you may have realized, I only happened to add some arrz and related code export samples. In this context I cared for deterministic subroutine order on code generation. I...

@GitMensch Deal, thank you very much. The code export test would indeed basically mean to start the export with defined preferences in batch mode and textually to compare the results....

@GitMensch With the new version 3.30-06 there are two export setting files now in folder `samples/export`. They differ just in the "line number" setting for BASIC export: `export_basic0.txt` produces vintage...

The (partial) type analysis and declaration support has come much later than the raw input evaluation. Therefore this temporary inconsistence. Thanks for the issue. I will consider it.

I would like to add that on assignments the data type isn't actually checked, either. Traditionally, the Executor has always allowed "re-typing" like in an untyped language: An instruction sequence...