Re: Proposed new preprocessor usage scheme for 4.0
- Posted by DerekParnell (admin) Jan 30, 2011
- 1386 views
One particular concept, which although it has never been made official is currently supported by the current 4.0 preprocessor handler, is that each preprocessor is given a unique file extension and that the different preprocessors input and output are kept separate from each other.
...
Of course, this is not so useful if your goal is to be able to add features X, Y and Z from preprocessors A, B, and C and then use those features anywhere and everywhere in your code ...
Which was exactly what I was referring to. The 'file extension' idea is both a useful and a useless idea - depending on what you are trying to achieve. It is useful when a complete file has been written in the 'pre-processor' (domain specific language) code but not so useful when you are 'cherry-picking' pre-processor functionality.
The swap concept could be implemented with either a text macro sub-language or an AST macro sub-language ... or as a native built-in operator.
