Recent changes to bugs

Compiler and asp dll problems

Enrico Scelsa — Tue, 12 Jul 2005 18:33:46 -0000

Memory problems when compiling, after first compile
step.
This is because the compiler modifies the compiled
source which launches it, and we think that this is not
very well accepted by the IIS asp dll.
This problem is present ONLY during compilation, and
not during normal operation, and is particularly evident
during debug of not yet completely compiled application.
For large compilation it is better to manually restart the
IIS at every compile step, disabling the autocomplete
compilation option.
In this case, for every directive which requires further
compilation steps (includes tag, classes casting..) the
user will have to launch the compiled executable
manually, for every subpart of the application.
This problem is due to the fact that some of the
parameters of all the directives are variables, and need a
runnning application in order to be compiled.
So, at the first run of the executable, it can happen that
it has to restart a compiler session, through a compiler
call inside it, and then, at the end of the compilation
process, it has to modify itself, calling an external
application.
The problem has to be solved "downsizing" the
parameters freedom to string constants...
In this way, every compilation will be finished just in one
single step, and there wont be any more the need for
running the compiled application with pending further
subcompilations.

compiler minor problems

Enrico Scelsa — Tue, 12 Jul 2005 18:22:53 -0000

- before you launch a compilation, you have to manually
empty the "compiled" (or whatever you configured as the
compiled files destination directory) folder manually.

- before you compile an application, you have to
manually reset the static variables (entities)

Environment variables are translated in their value

Enrico Scelsa — Tue, 12 Jul 2005 18:09:46 -0000

Environment variables are sometimes translated in their
actual value and not written using their symbol.

This behaviour is not critical, but could affect the porting
of the compiled files on different machines (ex: from a
staging environment to a production environment).

At the moment, it seems that the Entities functions are
affected by this, but it could be a good idea to check
other sections also.

The variables affected are the APPLIPATH series (WEB,
DATA, ....)

Enrico