Craig..

Here is my contention... Folks rarely if ever directly ask for features to be removed from their app tools. In other words, folks don't come out and say, "gee, I don't want macro expansion anymore...remove it." There is more to the story. And, that story was not told here. From my experience, the topic of macro expansion comes up when folks ask for the VFP language to be compiled. They are then confronted with the possibility of losing macro expansion. In this case, macro expansion indirectly became the issue. Folks then back off.

If there is one example that counters to some degree what I have said here, it would be in the area of irrelevant language components. I have said directly, get rid of them. Then again, this too was indirect because I complain about the size of the runtime - a legitimate beef. I then ask what could be excised from the language. Obviously, those langauage elements that have been supplanted by new items or are just plain not used/required anymore should go.

The contention I have with you in this issue and issues of the past is how you say things so "matter of factly" The team is doing this, the team is doing that. Etc, etc, etc. I don't do that and trust me, I have a magnitudes more contact with them than you. I for one don't know all of the requests. And further, I don't really care. But for sure, the direct request of removing macro expansion is not one of them. If anything, the opposite is true because people don't want to give it up. And this I know for a fact. And for sure, you do not want to go a round with me on this.