ansaurus

Question

Answer 1

+10 A:

It does, if anyone ever uses your code on a server where short tags are disabled. I work with several servers where they are. Other than that though, no. Using the short version makes your script less portable though for the above mentioned reason. This may or may not be an issue for you.

This is another issue entirely, but related. If you are trying to generate certain types of files from PHP (XML is the candidate that comes up most often for me) then having short tags can be an issue. For instance, the following causes a PHP syntax error:

<?xml version="1.0" ?>

You must instead write the following on a server that has short tags enabled:

<?php echo '<?xml version "1.0" ?>'; ?>

Gah!

Matthew Scharley 2009-10-20 06:52:34

It's unusual to see short tags disabled. Have they ever explained why they have it disabled (or why it can't be enabled)? I suppose it *may* be good to enforce a team to only use the `<?php` way.

alex 2009-10-20 07:01:21

I'll agree that the vast majority have them enabled. But really, the only reason to use them is laziness anyway. I prefer to use the 'long' version myself. Personally, I usually disable them on my dev servers to catch out any third party scripts I use that use them. In my fairly general experience, it's generally not a good first sign about the general quality of the script if they use it (lazy, not aware of things, whatever it happens to be).

Matthew Scharley 2009-10-20 07:15:48

@Matthew Completely agree with you.

alex 2009-10-20 07:36:30

How about the short-tag <?=$value?> inside an html template? Comes very handy! ;)

Frankie 2009-10-20 12:16:24

I do use `<?=`. That said, I'd sooner give that up than try to fudge around with xml headers. It gets annoying when you write out what should be valid, but isn't because of a quirk in the PHP interpreter. `<?xml` != `<?php`!

Matthew Scharley 2009-10-20 12:39:48

Answer 2

A:

No difference it's just a matter of preference I think, plus why should it matter? it's just another 3 bytes.

Edit:

Forgot to say that you have to enable short hand in php.ini

lemon 2009-10-20 06:52:35

It does matter, since it's a matter of server configuration. I work on some servers where the second version wouldn't run.

Matthew Scharley 2009-10-20 06:53:37

Yeah forgot to say that you have to enable it.

lemon 2009-10-20 06:54:26

Answer 3

A:

the closing bracket is not compulsory

Natrium 2009-10-20 06:53:30

Only if there's nothing else after the PHP code of course, which is unspecified/irrelevant in this question.

deceze 2009-10-20 06:59:00

This only applies to the very last PHP code block in a file.

alex 2009-10-20 06:59:07

@deceze: ofcourse

Natrium 2009-10-20 07:00:47

Downvoted because it missed the question.

Tom 2009-10-20 13:04:29

Answer 4

A:

On some systems, the default option for the short_open_tags is off, so the latter doesn't work, while the former does, so it can completely break your website if you use the second. Personally, I just like to override the setting and use the second.

FryGuy 2009-10-20 06:54:02

Answer 5

+4 A:

If your project is likely to be deployed on different servers (open source software, for example) it is best to always use <?php

However, if you're like me, and always strive for maximum portability, use <?php even if you don't believe your software will ever leave your server. Most servers have short tags enabled.

However, if they have short tags disabled, and you use them, your PHP will be exposed to the world (if under the document root).

alex 2009-10-20 06:54:48

Answer 6

A:

<? ?>

are short tags, if short tags are off it won't work.

Geshan 2009-10-20 08:05:52

ansaurus

tags:

views:

answers:

<?php vs <? ...Does it matter?

related questions