Vincent.....anyone else! Read

Anon

Ok my bud Interactive and I are in a argument.

printf("<option value=%s?bus_id=%s>%s</option>",$row['css'],$row['bus_id'],$row['address']);

or is it:

printf("<option value=%s?bus_id=%s>%s</option>",$row["css"],$row["bus_id"],$row["address"]);

?????

Assume that all connections work and everything is good. Both do work. But is one perfered or more "ethical" over another? Thanks! Vincent would love to hear from you on this one. Also anyone else. Also the manual says nothing about the proper way. Thanks!
Ziggs

brandonschnell

the first method wouldn't work with variables, ie:

$row['$var']

wouldn't work as you would expect. php wouldn't convert the variable to whatever $var contains.

using single quotes in php (this doesn't apply to sql statments) is slightly faster than double quotes. personally i'd recommend double quotes if only to maintain coding consistency.

interactive

now he's talking abut fetching a row and the row name being i guess what you put as var you should pay attention you know? lol and im right ziggs...

interactive

oh ya and one more thing he had a print function running where it was going like printf "<OPTION VALUE='value'>".$row["row1"],$row["row2"];
i was telling him that he should use single quotes instead of double one becuase they are faster and two if he went back add some text after the variables were calling (["row1"],$row["row2"]."text here"😉 that he should use double quotes that way it wouldn't throw back a parse error.

[deleted]

The 'proper' way is with single quotes, becuase PHP will not attempt to parse data inside single quotes, which makes it faster.

Marginally faster, as in: "you'll never know until your server is stuck on 0.1% idle"

There's not wrong and right here, it's just 'cleaner' to use single quotes if you do not need to process the data inside the quotes.

As for adding more text later, that really does not matter, because that will have it's own quotes to.

A forum, a FAQ, email notification, what else do you need?

Time to YAPF!: http://www.yapf.net/

dar-k

Hi there.
I wonder is there's anything wrong with my method.
Instead of writing like this:

printf("<option value=%s?bus_id=%s>%s</option>",$row['css'],$row['bus_id'],$row['address']);

or this:

printf("<option value=%s?bus_id=%s>%s</option>",$row["css"],$row["bus_id"],$row["address"]);

I'd write it down like this:

printf("<option value=%s?bus_id=%s>%s</option>",$row[css],$row[bus_id],$row[address]);

No quotation at all. Usually works for me.
U ppl see any problems with this method?
Thnx.

Anon

Thats the weird thing. See all work (I dont know Dar-K) but why do you use ' instead of "? B/C its faster? I understand completely Vincent about being barely faster. Oh and Interactive....we are both right. It works my way and it works yours. Congrats. 🙂 So yours runs .01% faster! Laudy Freakin Dah! HAHA. Thanks for your insight Brandon and Vincent. I dont know about you Dar-K. I have never did it like that and two books use " instead of ' so I just did it the way the books told me. The books are PHP Cookbook, and WROX "Beginning PHP" so I thought they would both have a freaking clue. Also the WROX book is written by 5 individual programmers and they all use " instead of '. So hmm... odd. 🙂 Ok thanks everyone. Lata!
Ziggs

Anon

lol ok were both rigth i agree but still i strongly recommend using single for obvious reasons draw...

[deleted]

You defineately NEED quotes.

If you don't use quotes, PHP assumes you meant to use a constant. And if you use an undefined constant, PHP uses the name of the constant as it's value.

If you put

error_reporting(E_ALL);

at the top of your script you'll see a sh*tload of warnings about this.

it 'works' only because PHP for some strange reason falls-back to using the name of the constant as the value, giving the same effect as entering a quoted string.

But it is thuroughly wrong. 🙂

dar-k

Grrr...
That WAS a sh*tload of warnings!
I guess I better fix exisiting work before a new version of PHP ruins it all.
Thnx, Vincent.

So, I could always get away with it as long as the warnings are off?

interactive

dont you think it might slow down the script hu?

dar-k

Let me put it like this:
I started off with ASP and Access databases.
Now I work with PHP and MySQL on a daily basis.
If PHP slows down a bit, I don't think I'll really notice. :-)

[deleted]

lol

Uhm no, doing 10 var checks does NOT slow you down at all.

But in the end it's up to you to choose:
- An unnoticably slower script that works 100%
or
- An unnoticably faster script that fails at random intervals without producing any error reports.