From: Philip S. <ph...@se...> - 2006-10-27 16:35:10
|
Hi all, I'm interested in experimenting with the [[.compact]] directive. I have a lot of .spy files and rather than modifying them all, I would like to be able to control compaction via a central location -- spyceconf.py would be ideal. Here are the three possibilities that I see in order of best to worst: 1) A line or two of spyceconf.py magic that I haven't yet figured out. (Perhaps via some abuse of globaltags?) 2) Modify all of my .spy files to include some sort of "if global compaction setting is on: [[.compact]]". (Bad syntax but you get the idea.) 3) Modify all of my .spy files to add or remove [[.compact]] each time I want to change it. (Yuck.) Suggestions appreciated. Thanks Philip |
From: Jonathan E. <jon...@ca...> - 2006-10-27 17:38:41
|
On Fri, 27 Oct 2006 12:34:58 -0400, "Philip Semanchuk" <ph...@se...> said: > Hi all, > I'm interested in experimenting with the [[.compact]] directive. I have > a lot of .spy files and rather than modifying them all, I would like to > be able to control compaction via a central location -- spyceconf.py > would be ideal. Here are the three possibilities that I see in order of > best to worst: > 1) A line or two of spyceconf.py magic that I haven't yet figured out. > (Perhaps via some abuse of globaltags?) Compact is a compiler directive, not a runtime thing. Which is good because it's fast but bad because it's very limited. You'd have to hack the compiler if you wanted to make this global. Personally I would rather remove it completely and force using runtime filters instead. > 2) Modify all of my .spy files to include some sort of "if global > compaction setting is on: [[.compact]]". (Bad syntax but you get the > idea.) Also won't work. The if is runtime, the .compact is compile-time. > 3) Modify all of my .spy files to add or remove [[.compact]] each time > I want to change it. (Yuck.) Yeah, yuck. :) -- C++ is history repeated as tragedy. Java is history repeated as farce. --Scott McKay |