I found problems with some settings, obtained from current_settings at program start (command line processing...). At that time no (module/parser) object exists, that could hold *current* settings. Instead some of the members of TSettings should be read only from init_settings, like disabledircache, cs_link_on_target...

Can somebody review the members of globals.TSettings, for which of them are really for change during compilation?

The offending elements can be found by running the current version of the NoGlobals branch, with any source file - all errors occur before a source file is selected for compilation.

In a future compiler version TSettings should be updated, to exclude members that should not be subject to local changes. This change may deserve changes to the ppu file writer as well?

DoDi