In our previous episode, Ryan Joseph said: > > > > I've done my fair share of language advocacy in the past and in general am > > no friend of C, but I suggest that a number of people- on both the "pure" > > and the "pragmatic" sides of the argument- could very much do with "cooling > > it". > > I don?t understand why there's so must resistance to letting programmers > make ugly macro hacks if they want to.
There is no resistance against using macro hacks. Use six layers of preprocessors if you want to. There is only resistance against us implementing and maintaining it. And fix the zillions of corner cases which will all come with similar reasoning as yours. We simply want to avoid spending the time on a major feature that we don't believe in. > Why does anyone care if I have some edge case and I need a solution > quickly which macros fulfill? The compiler should be helpful, not force > into some programming paradigm and best practices etc.. etc? Why do we have to cater for every hypothetical edge case that you could encounter? Tomorrow somebody wants space idented blocks to easier borrow code from Python (and we will also tell him to take a hike). _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
