The interpretor seems to be cacheing the environmental change of frontend files that have exactly the same code and worked upon exactly the same state variables - and thus not executing the files if the result is cached already.
I wrote that in very general terms as I don't know exactly what it is doing. So explained loosely from my point of view...
My system has lots of files sitting in different directories that are identical. These files should execute differently because they execute as a function of the directories they are in. They are all frontends to my system, and the directory that they are in specifies what aspect of the system is called up.
