Re: <?xml tags (was PDM Meeting Notes)

Hello Mike, Same at my company. <?php= would be very nice. -- Best regards, Jason mailto:jason@ionzoft.com Wednesday, November 30, 2005, 4:31:58 AM, you wrote: MH> Just FYI, the lack of <?php= is the only reason we don't disable short MH> tags on all development projects at my company. MH> Mike MH> On Mon, 28 Nov 2005 20:29:42 +0100 MH> Marcus Boerger <helly@php.net> wrote: >> Hello Bastian, >> >> id like to see '<?php=' too. >> >> marcus >> >> Monday, November 28, 2005, 9:56:56 AM, you wrote: >> >> > What concerns me most is that <?php= does not work, regardless if short >> > tags will be disabled or not in php6. I currently use <%= to counter >> > this, but I am most certainly *not* happy with it. >> >> > So a clean <?php= solution would be ideal, so I wouldn't have to care >> > about xml/xsl files parsed and neither about my templates growing too >> > large because of php overhead. >> >> > Sara Golemon wrote: >> >>> I recall this being discussed before, but not what came of it: is there >> >>> a problem with just ignoring <?foo where foo is anything other than php >> >>> or =? <?foo or <?bar or <?whatever is a parse error anyway so I very >> >>> much doubt there's any BC break. Unless someone's program relies on >> >>> parse errors. >> >>> >> >> The problem there becomes legacy support for: >> >> >> >> <?foo();?> >> >> >> >> And before you say "just watch for parens" there's also: >> >> >> >> <?foo::bar();?> >> >> >> >> and a much more insiduous example: >> >> >> >> <?die ?> >> >> >> >> no semicolon, no parens, no paamayim nekudotayim, nothing but a >> >> perfectly valid looking PI tag. >> >> >> >> -Sara >> >> >> >> >> Best regards, >> Marcus >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php MH> Mike Hall MH> Twist Digital Media MH> e. mike.hall@twistdigital.co.uk MH> D I S C L A I M E R MH> Statements and opinions expressed in this e-mail may not represent those MH> of the company. MH> The information transmitted is intended only for the person or entity to MH> which it is addressed and may contain confidential and/or privileged MH> material. Any review, retransmission, dissemination or other use of, or MH> taking of any action in reliance upon, this information by persons or MH> entities other than the intended recipient is prohibited. If you MH> received this in error, please contact the sender immediately and delete MH> the material from any computer.