Re: planning future BC Breaks - was Re: [PHP-DEV] fatal static call in php 6.0?

Hello Christian, first of all c would be enough. Preprocessing has nothing to do with c++. Also a lot of compilers allow to use the pre-process stand alone. And then there is this one little disadvantage. A c compiler doesn't know that it is not supposed to deal with stuff outside <?php...?> and last but not least loading a c compiler is not always possible...since it would allow to use it, which is potentially dangerous. And at last it takes forever having to load a c compiler everytime you want a php script preprocessed. best regards marcus Sunday, May 28, 2006, 8:26:57 PM, you wrote: > William Candillon wrote: >> I think that a macro will be a very nice and powerful solution to this >> problem but according to me it needs to be done by an external tool. > That already exists ;-) > Try > cpp -w -P -C <in.php >out.php 2>/dev/null > if you don't want to reinvent the wheel :-) > Marcus Boerger <helly@php.net> wrote: >> what you propose would mean a lot of changes to the php code and >> and the zend engine. The pre processor to allow this will be written >> as an extension and that extension will have no impact on anybody >> that doens't like it simply becuase you can disable extensions. > I'm all for making it an extension which is not included in the main > PHP. But your point is invalid because if a preprocessor can be done as > an extension then so can be my version: It is nothing but a *very* > stripped down preprocessor after all. > Anyway, I don't really care too much about how such a preprocessor is > done as long as a) it's not bundled with PHP by default and b) is not > used as an excuse to make incompatible syntax changes without compelling > reason. > Regards, > - Chris Best regards, Marcus