2009/1/11 karl williamson <public@khwilliamson.com>: >> > I have been thinking about this some more, and wonder if the definition of > "use feature" could change so that it encompasses more than just syntax, but > other things like semantic changes we think may break existing code. And > that some things that this enables may change in the future to be enabled by > default, and one has to say "no feature 'xxx'" or "no feature ':5.12' to > keep the old behavior. > > Then we wouldn't need a legacy pragma, but feature would suffice for both > sorts of things. We could then at some point, for example, make "say" > enabled by default. > > But it does mean expanding the meaning of 'feature'. What do you think? Nobody replied to this, so here's my thoughts... That could work, but I don't find this pretty, and possibly confusing.Thread Previous | Thread Next