hi here are some php things i want to tell you

[Agnostic Bear]

1) security comes before performance in all aspects of programming, php or not
2) learn to love () ? : (ternary operator)
3) use "and" and "or" instead of && and ||, much easier to read and understand, does exactly the same thing
4) never use $_REQUEST, very easy to forge things
5) "" and '' perform the same, stop being eejits and saying one performs faster than the other, they don't any more, use either
6) use , instead of . in echo, it's faster
7) use echo instead of print unless you want to hang on to the variable, it's faster
8) use cookies instead of sessions unless you specifically need sessions
9) use strstr instead of foreach / for loop for replacing things

that is all you can go now

[Skajo]

completely went over my head.

[Fehm]

Lol it'll come in handy Im sure ;)
I think you should right a guide on PHP security :P Because the only things I know are stripslashes and mysql_real_escape_string, md5 and sha1 :L:L

?:)

[DeejayMachoo$]

There are some things I thought I should point out in your post.

Number two it's really personal preference although I must agree that when assigning variables with the ternary operator it does look nicer.

Number three is iffy, yes they're easier to read and understand, but there is a slight difference between them. The "&&" and "||" have a higher operator precedence than "AND" and "OR", but most people won't encounter a situation where this will be a problem.

Number five is wrong, single quotes are faster unless you concatenate which then in most cases double quotes is faster. But the speed difference is negligible.

Number seven is confusing, you say use echo instead of print unless you want to hang onto the variable? If you echo a variable, it doesn't unset it, same goes with print - either way you'll hang onto it.

Number eight I can disagree with, because cookies can be more easily manipulated than sessions, so you need to justify when you should use cookies over sessions - and this contradicts with number one, as by using sessions it's more secure than cookies in most cases.

[Agnostic Bear]

There are some things I thought I should point out in your post.

ok


Number three is iffy, yes they're easier to read and understand, but there is a slight difference between them. The "&&" and "||" have a higher operator precedence than "AND" and "OR", but most people won't encounter a situation where this will be a problem.
Nobody will ever encounter a situation where that will be a problem, I can see no reason for it ever to be a problem ever.


Number five is wrong, single quotes are faster unless you concatenate which then in most cases double quotes is faster. But the speed difference is negligible.
No. Single quotes are as fast as double quotes and vice-versa, I don't consider 0.007 seconds faster over 100,000 loop test to be faster, I consider it to be the same time.


Number seven is confusing, you say use echo instead of print unless you want to hang onto the variable? If you echo a variable, it doesn't unset it, same goes with print - either way you'll hang onto it.
print holds the printed string in a variable, echo doesn't


Number eight I can disagree with, because cookies can be more easily manipulated than sessions, so you need to justify when you should use cookies over sessions - and this contradicts with number one, as by using sessions it's more secure than cookies in most cases.

no they're not, cookies are just as secure as sessions if you know how to keep them secure, sessions are based on a cookie with the session id anyway

[BoyBetterKnow]

1) security comes before performance in all aspects of programming, php or not
Naturally.
2) learn to love () ? : (ternary operator)
Have married it.
3) use "and" and "or" instead of && and ||, much easier to read and understand, does exactly the same thing
Mm. Personal preferance IMO, I use | and & and they work fine.
4) never use $_REQUEST, very easy to forge things
mmhm.
5) "" and '' perform the same, stop being eejits and saying one performs faster than the other, they don't any more, use either
I think that ' looks nicer. Personal pref.
6) use , instead of . in echo, it's faster
How much faster?
7) use echo instead of print unless you want to hang on to the variable, it's faster
already do
8) use cookies instead of sessions unless you specifically need sessions
Use both...
9) use strstr instead of foreach / for loop for replacing things
fairs

that is all you can go now

CHEERS JEWISH BEAR.

[Iszak]

No. Single quotes are as fast as double quotes and vice-versa, I don't consider 0.007 seconds faster over 100,000 loop test to be faster, I consider it to be the same time.
Although you may not consider it to be faster - it is faster none the less, but I agree with Matt, it's negligible.



print holds the printed string in a variable, echo doesn't
No it doesn't, It doesn't specify it in the documentation, I can't find it anywhere, prove me wrong?



cookies are just as secure as sessions if you know how to keep them secure, sessions are based on a cookie with the session id anyway
I'm not even going to argue with this - cookies shouldn't be used for sensitive data no matter how much you can "secure" it with encrypting or hashing and I think that's what Matt was getting at.

[Agnostic Bear]

Although you may not consider it to be faster - it is faster none the less, but I agree with Matt, it's negligible.
0.007 over 100,000 loops is not faster in a real-world situation.



No it doesn't, It doesn't specify it in the documentation, I can't find it anywhere, prove me wrong? It returns 1 always, so you can set it in a variable, forgot to add "printed string 1" obviously >.>



I'm not even going to argue with this - cookies shouldn't be used for sensitive data no matter how much you can "secure" it with encrypting or hashing and I think that's what Matt was getting at.
Awesome, you should stop using every forum and website in the world that uses cookies for sensitive data (which is: nearly every website that uses cookies).

This forum, every forum you've ever been on. Cookies are as secure as the computer they're stored on, which in my case happens to be very.

[Devestation]

Wow dan, not much more to teach someone in 10 seconds now is there?
Thanks for these tips - They'll help with my PHP skills.

[Iszak]

Dan, grow the **** up - I don't know if it's just me, but I'm sick of your constant trolling, and pointless threads that seem as if they're just to get "praised" for a few hours of work.

Don't bother replying to this, because I'm never going to reply to you again.

[Jamesy]

Dan, grow the **** up - I don't know if it's just me, but I'm sick of your constant trolling, and pointless threads that seem as if they're just to get "praised" for a few hours of work.

Don't bother replying to this, because I'm never going to reply to you again.

I don't think its trolling by giving information straight and to the point in a way that anyone can understand.

[BoyBetterKnow]

I don't think its trolling by giving information straight and to the point in a way that anyone can understand.

I think Iszak meant like the KP preview dan posted aswell etc.

[DeejayMachoo$]

I don't think its trolling by giving information straight and to the point in a way that anyone can understand.

But when it's infomation thats;

1) So simple anyone with a single brain cell knows it.
or
2) Wrong.

[Mentor]

1) security comes before performance in all aspects of programming, php or not
Totally disagree, some times performance is far more important. The balance between performance and security is important to get right and can only ever be judged on a case by case basis.


2) learn to love () ? : (ternary operator)
3) use "and" and "or" instead of && and ||, much easier to read and understand, does exactly the same thing
Kinda a contradiction, Ternary operators are often harder to read that simple if's or cases. On the flipside id say && or || is actually easier to read than writing the word "/


4) never use $_REQUEST, very easy to forge things
True, no real reason to ever use it ether

5) "" and '' perform the same, stop being eejits and saying one performs faster than the other, they don't any more, use either
Very wrong, they perform two different actions and '' is upto a factor of 4 faster... Double quotes include parsing of variables within it, single quotes just passes a string o.0


6) use , instead of . in echo, it's faster
The speed saved here would be lost totally by taking your advice above?


7) use echo instead of print unless you want to hang on to the variable, it's faster
Print is often faster?

8) use cookies instead of sessions unless you specifically need sessions
Sessions are more secure + store more data and data-types than cookies are capable of ?

9) use strstr instead of foreach / for loop for replacing things
Or use somthing that replaces strings like str_replace?

... Whut?


Wow dan, not much more to teach someone in 10 seconds now is there?
Thanks for these tips - They'll help with my PHP skills.
No... it really wont, almost all of it was dead wrong?


0.007 over 100,000 loops is not faster in a real-world situation.
Yea as dealing with huge amounts of data is a thing a company would never ever come across in the real world (much larger than a 100,000)... What planet did you say you were from?


I don't think its trolling by giving information straight and to the point in a way that anyone can understand.
Seeing as its mostly totally wrong, i think its probably worse than most trolling as people are actually believing it

Comic book guy: Worst php tutorial.. ever

[Source]

Dan, grow the **** up - I don't know if it's just me, but I'm sick of your constant trolling, and pointless threads that seem as if they're just to get "praised" for a few hours of work.

Don't bother replying to this, because I'm never going to reply to you again.

Says you... the person who likes and loves to argue about anything and everything PHP/html/ruby/js (the list can go on).

Anyway, these tips are very helpful for the people just learning PHP... and even more advanced members.

[Mentor]

Says you... the person who likes and loves to argue about anything and everything PHP/html/ruby/js (the list can go on).

Anyway, these tips are very helpful for the people just learning PHP... and even more advanced members.
If by learn php, you mean fail at then yes? These tips are almost all wrong, and whats not is essentially useless common sense. Anyone other than a total php noob who cant see this is seriously over estimating there php skills.. Why are people defending these tips? has no one actually read them?

Also, ad hominem really isn't helpful, hes right whether or not you like him and whether or not he likes to argue. Facts stay the same regardless of who's telling you them...

[BoyBetterKnow]

Dan, you didn't say anything about <? being faster than <?php
...

@thybag It's just his personal prefs he's posted saying they are tips rly :P

[Agnostic Bear]

Totally disagree, some times performance is far more important. The balance between performance and security is important to get right and can only ever be judged on a case by case basis.
This "balance" you speak of is nothing but a scapegoat for coders to get out of ******* up, if you have a gigantic database and someone strolls in there and deletes everything because you made this little bit of code faster by removing a check, you're gonna be enjoying hours of work restoring backups. There is no balance, security always comes before performance, if you can't get it to perform fast enough with the security, throw more servers at it.


Kinda a contradiction, Ternary operators are often harder to read that simple if's or cases. On the flipside id say && or || is actually easier to read than writing the word "/
I never said they were easy to read, I find them to be better than simple if/else statements, personal opinion there. I said or/and is easier to read, and it is, if you get an average joe and slap them && || "and" or "or", which are they going to understand without any coding/programming experience? (hint: it's and/or)



Very wrong, they perform two different actions and '' is upto a factor of 4 faster... Double quotes include parsing of variables within it, single quotes just passes a string o.0
Maybe at php 4.3 sure, but not with php 5 + 4.3 (i think it's 4.3, don't quote me on it), the performance differential is completely eliminated.



The speed saved here would be lost totally by taking your advice above?
question is answered above



Print is often faster?
print is never faster as it has to return after it's done (always returns 1)


Sessions are more secure + store more data and data-types than cookies are capable of ?
data types in php are stupid and always have been, the only reason you ever need data type storage in php is for strict comparisons, strings are fine for everything in a real-world situation



Or use somthing that replaces strings like str_replace?
my bad, i meant strtr


attn all: i only work with real-world situations nowadays, i don't bother with benchmarks and testing scenarios, as they're utterly useless when building apps and such

now if you'll excuse me i have a can of coke to drink

[Excellent2]

Not going to comment on the PHP as I really don't know all that about it. I have to agree with Iszak though.. your posts are stupid and sarcastic at the best of times.

[Mentor]

This "balance" you speak of is nothing but a scapegoat for coders to get out of ******* up, if you have a gigantic database and someone strolls in there and deletes everything because you made this little bit of code faster by removing a check, you're gonna be enjoying hours of work restoring backups. There is no balance, security always comes before performance, if you can't get it to perform fast enough with the security, throw more servers at it.
That or someone working in the real world in part of an application where speed is critical and checking an inputs a waste of time as the db has no write access anyway...
But i'm guessing you aint come across the real world yet. When your working with 10's or millions of records, these things count.


I never said they were easy to read, I find them to be better than simple if/else statements, personal opinion there. I said or/and is easier to read, and it is, if you get an average joe and slap them && || "and" or "or", which are they going to understand without any coding/programming experience? (hint: it's and/or)
With no coding experience, thay ain't going to under stand the sql syntax to start with, so thats kinda a null point. If not easier to read, faster or anything else - what exactly makes them better?


Maybe at php 4.3 sure, but not with php 5 + 4.3 (i think it's 4.3, don't quote me on it), the performance differential is completely eliminated.
No, with php 5 (and 4 too, and 3... well all php), and for obvious reasons? Obviously it depends on setup, but as a rule when writing fast php code, it makes the difference.


question is answered above
You loose alot more speed with that, than you gain here. The difference between "" and '' is still very real...


print is never faster as it has to return after it's done (always returns 1)
Below 10,000 items its often faster, over that though echo will normally overtake in terms of speed. Setup and usage there for makes the difference


data types in php are stupid and always have been, the only reason you ever need data type storage in php is for strict comparisons, strings are fine for everything in a real-world situation
That or for using Object Oriented code? you know OOP? being able to store a live object directly is a big advantage..


my bad, i meant strtr
The speed difference here is still less than the difference between "" and ''


attn all: i only work with real-world situations nowadays, i don't bother with benchmarks and testing scenarios, as they're utterly useless when building apps and such
I take it you've never had a real job in IT? Because your version of non-real world scenarios are things i deal with dayly o.0

[BoyBetterKnow]

This is a good little debate.

I think using ' is much better than ". But depending on what you wanna do really. I can't think of a situation where I use " over '.

Also when i want to do echo I usually strip the string into each individual letters as they get put into an array and I echo them out individually to improve performance.

BTW I WS JKING

[Mentor]

This is a good little debate.

I think using ' is much better than ". But depending on what you wanna do really. I can't think of a situation where I use " over '.

Also when i want to do echo I usually strip the string into each individual letters as they get put into an array and I echo them out individually to improve performance.

Well there is an advantage to useing ", as you can just have a line like "hello {$username}, whats up?"; as opposed to 'hello '.$username.', whats up?';
Which does add to readability and can speed up coding. All really depends on what your doing and when, both have there place :)

[Agnostic Bear]

That or someone working in the real world in part of an application where speed is critical and checking an inputs a waste of time as the db has no write access anyway...
But i'm guessing you aint come across the real world yet. When your working with 10's or millions of records, these things count.
Yes a database with 10s of millions of records isn't going to have write access when it's handling huge amounts of data, well done.



With no coding experience, thay ain't going to under stand the sql syntax to start with, so thats kinda a null point. If not easier to read, faster or anything else - what exactly makes them better?
Your mind understands it faster (less than 0.0000000000000001 of a second faster! but that obviously still matters when your brain can process trillions of signals a second, just like a computer) because it's part of your mother tongue, just like and and und, your brain will always recognise and faster (if you're english, or und if you're german) because it's part of your "base programming" if you will it doesn't matter which, and as i said it's a matter of preference.


No, with php 5 (and 4 too, and 3... well all php), and for obvious reasons? Obviously it depends on setup, but as a rule when writing fast php code, it makes the difference. it doesn't make the difference at all, i've never seen any application that prints/echos something over 100 times



You loose alot more speed with that, than you gain here. The difference between "" and '' is still very real... see above, nobody cares about the differences any more, it's not real unless you're messing with several hundred thousand strings in 1 script, which never happens.



Below 10,000 items its often faster, over that though echo will normally overtake in terms of speed. Setup and usage there for makes the difference
print is never faster than echo because it always returns 1, i will continue to drill this into your head until you understand RETURNING IS SLOWER THAN NOT RETURNING



That or for using Object Oriented code? you know OOP? being able to store a live object directly is a big advantage..
storing objects in a session is stupid, why would you ever do that? i can understand integers, booleans, arrays and strings, but not objects



The speed difference here is still less than the difference between "" and ''

"usually, its preferable to use str_replace, but when you want to replace many characters for many others characters (and not only a value) strtr is better." note i didn't say always in my post, nor did i say anything about a speed difference



I take it you've never had a real job in IT? Because your version of non-real world scenarios are things i deal with dayly o.0
my situations are logical, easy to understand and easy to comprehend, you're going on about differences that only happen in the poorest of code, i do believe my situations are far more real-world than yours

[Mentor]

Yes a database with 10s of millions of records isn't going to have write access when it's handling huge amounts of data, well done.
I have no idea if your being sarcastic or not, but yea, thats pretty danm common? whats your point?


Your mind understands it faster (less than 0.0000000000000001 of a second faster! but that obviously still matters when your brain can process trillions of signals a second, just like a computer) because it's part of your mother tongue, just like and and und, your brain will always recognise and faster (if you're english, or und if you're german) because it's part of your "base programming" if you will it doesn't matter which, and as i said it's a matter of preference.
You may wana go look at some German programming... (tip: it aint in german)


It doesn't make the difference at all, i've never seen any application that prints/echos something over 100 times
Yup, what script ever has ever output more than a 100 things... You don't believe in objects so i'm gonna guess in your code every time you show the top 100 members you get that?


see above, nobody cares about the differences any more, it's not real unless you're messing with several hundred thousand strings in 1 script, which never happens.
700,000 string? Thats a lot less than i often find myself messing with. You know what i was saying about those databases. Some companies have alot of transactions... Generating live stats reads alot of data and takes a while, those milliseconds start to count

[quote]print is never faster than echo because it always returns 1, i will continue to drill this into your head until you understand RETURNING IS SLOWER THAN NOT RETURNING
They handle buffering differently, so not entirely true :)


storing objects in a session is stupid, why would you ever do that? i can understand integers, booleans, arrays and strings, but not objects
If you don't understand oop i have trouble considering you as a programmer..


"usually, its preferable to use str_replace, but when you want to replace many characters for many others characters (and not only a value) strtr is better." note i didn't say always in my post, nor did i say anything about a speed difference
What makes this better?


my situations are logical, easy to understand and easy to comprehend, you're going on about differences that only happen in the poorest of code, i do believe my situations are far more real-world than yours
I really, really doubt that. You see, my situations happen in the real world, with real data, for real people, under real deadlines, on machines with real specs and need to work in real time. Duno how you get much more real o.0

I'm starting to follow Iszak's thinking as this is getting dull...

[Agnostic Bear]

I'm starting to follow Iszak's thinking as this is getting dull...

yes this is getting dull because you are making complex points about simple things

to put it simply:
returning is always slower than not
i use objects in everything that needs it (storing objects in sessions is not needed)

i am going to leave you to your fantasy world situations where every server is a pentium 3 with less than 1gb of ram and every database does 10 quintillion queries a nanosecond to listen to some brian eno and get some coding done and chat to people about things

using latin and such isn't smart nor impressive, using simple language that everyone can understand and get to grips with even though you can use such language is

uh and scalability is more important than speed anyway bye

[Mentor]

i am going to leave you to your fantasy world situations where every server is a pentium 3 with less than 1gb of ram and every database does 10 quintillion queries a nanosecond to listen to some brian eno and get some coding done and chat to people about things
Ha... if you only knew what the corporate world was like... are staging server has less than those specs :p Efficiency is key, fortunatly the db runs on a much faster cluster in the main data center so we just uses views to perform all the querying and main statistical processing sql side :)

using latin and such isn't smart nor impressive, using simple language that everyone can understand and get to grips with even though you can use such language is

uh and scalability is more important than speed anyway bye
If your systems slow and inefficient, it wont scale o.0

Who was using Latin? I got lost on that point.

[Agnostic Bear]

Ha... if you only knew what the corporate world was like... are staging server has less than those specs :p Efficiency is key, fortunatly the db runs on a much faster cluster in the main data center so we just uses views to perform all the querying and main statistical processing sql side :)
you need a better business if your staging server is that poor



Who was using Latin? I got lost on that point.
you did, "ad hominem"

[Mentor]

you need a better business if your staging server is that poor
Playing my work place is bigger than yours seems kinda stupid... Then again, i kinda suspect your work only includes some mates giving you a few quid to bash out a crappy site every now and then "/


you did, "ad hominem"
Ah... Sorry to tell you thats English, it just comes from Latin. You start banning words that we imported from other countries and your dictionaries gonna be very very small.

[Agnostic Bear]

Playing my work place is bigger than yours seems kinda stupid... Then again, i kinda suspect your work only includes some mates giving you a few quid to bash out a crappy site every now and then "/

i don't do php for funds or profit, i find it's better to be open source with open source languages



Ah... Sorry to tell you thats English, it just comes from Latin. You start banning words that we imported from other countries and your dictionaries gonna be very very small.
it's latin

[Mentor]

i don't do php for funds or profit, i find it's better to be open source with open source languages
Is that your way of saying you flip burgers for a living?


it's latinYea.. so's octopus :rolleyes:

[Agnostic Bear]

Is that your way of saying you flip burgers for a living?

Yea.. so's octopus :rolleyes:

Yes octopus isn't spelt the same way they do in latin though, it's like saying quad erat demonstrandum is english, it's not, it's latin and always has been.

http://en.wikipedia.org/wiki/List_of_Latin_phrases_%28full%29

looks like ad hominem is on there, just like q.e.d.

and uh no i don't work i chill out all day

[Mentor]

Yes octopus isn't spelt the same way they do in latin though, it's like saying quad erat demonstrandum is english, it's not, it's latin and always has been.

http://en.wikipedia.org/wiki/List_of_Latin_phrases_%28full%29

looks like ad hominem is on there, just like q.e.d.

and uh no i don't work i chill out all day
Kinda explains that "real world" experience of yours. Also, believe it or not, i wasn't just saying "to the man" in Latin, its English meaning is different as in it refers to the logical fallacy.. the wikipedia page actually explains that?

[Agnostic Bear]

Also, believe it or not, i wasn't just saying "to the man" in Latin, its English meaning is different as in it refers to the logical fallacy.. the wikipedia page actually explains that?

using it as a logical fallacy changes approx. nothing. ad hominem is latin and always will be, it's like saying bonjour is english because a lot of british people use it

[Mentor]

using it as a logical fallacy changes approx. nothing. ad hominem is latin and always will be, it's like saying bonjour is english because a lot of british people use it
Or the term alter ego - thats latin after all... Hey, wait just a second! we do use that :O what a shock..

[Agnostic Bear]

Or the term alter ego - thats latin after all... Hey, wait just a second! we do use that :O what a shock..

Your lack of understanding of simple English is infuriating, I didn't say we didn't use ad hominem, I said it was Latin not English, just like alter ego, id est (i.e.), exempli gratia (e.g.). They're both Latin.

Please stop posting until you can grasp what I'm saying.

[Mentor]

Your lack of understanding of simple English is infuriating, I didn't say we didn't use ad hominem, I said it was Latin not English, just like alter ego, id est (i.e.), exempli gratia (e.g.). They're both Latin.

Please stop posting until you can grasp what I'm saying.

I'll point out you went from defending all you tips, too trying to save face by auguring that i dont understand english. Kinda reflects how well this is going for you..
English is a composite of many languages all that have contributed words towards it over time. Theres a reason we spell center centre, its because its originally French. If you remove every word that is taken fully or party from a previous language, English would have to few words to even class as a language in itself. Just because a word exists in another language, does not mean it doesn't exist in English as well..

This hasn't touched on php in quite a while, so is just heading further and further offtopic. Tips are wrong and should not be listened to. I'm gonna conciser this as pretty much proven so am calling it a night on this thread.

[Agnostic Bear]

I'll point out you went from defending all you tips, too trying to save face by auguring that i dont understand english. Kinda reflects how well this is going for you..
English is a composite of many languages all that have contributed words towards it over time. Theres a reason we spell center centre, its because its originally French. If you remove every word that is taken fully or party from a previous language, English would have to few words to even class as a language in itself. Just because a word exists in another language, does not mean it doesn't exist in English as well..

words that are in the english dictionary and are considered "english" are drawn over hundreds of years, they don't just magically pop into the english dictionary whenever someone uses the word, just like ad hominem, not enough people use it to be considered english, i.e + e.g (full phrases) are used a bunch by english people but aren't really english at all, it's all based on how it gets used / is it used by other cultures and what not

so i will say again, ad hominem isn't english, i.e and e.g aren't english and they wont be until we manipulate them into something english and usable, it has to sound english, feel english and be in the english dictionary to be english, i support i.e and e.g being english, but not the actual phrases behind them


This hasn't touched on php in quite a while, so is just heading further and further offtopic. Tips are wrong and should not be listened to. I'm gonna conciser this as pretty much proven so am calling it a night on this thread.

i'm actually just gonna go ahead and say you're at a loss here and all of my tips are right because they're just that; tips

[Black_Apalachi]

completely went over my head.

Me too, so I'm not going to get involved lol.

I'd just like to ask however, what makes a website "secure"? Since reading some of this thread, all I can imagine is getting my site finished and opened just to have it hacked... :S

[Source]

Secure would refer to script/site vulnerabilities/exploits (filtering user inputs etc ). Presuming no potential hosting flaws.

[Black_Apalachi]

Secure would refer to script/site vulnerabilities/exploits (filtering user inputs etc ). Presuming no potential hosting flaws.

Hmm.. so is there steps you should take when making a website or is there not much to worry about if you're keeping it pretty simple?

[J0SH]

Thank you for the tips :D

[Mentor]

Hmm.. so is there steps you should take when making a website or is there not much to worry about if you're keeping it pretty simple?
The risks really depend on how dynamic your site is, if you stick to static html your pretty safe, if you start adding php in, you do have to be careful, epically if your using a sql db, as sanitizing inputs is essential in stopping people being able to wreak havoc with your data :) Simlar situation to a lesser extent with if your writing to files :)

Chances are you dont need to worry, those with any real hacking ability likely wouldn't have any interest in attacking your site for no reason. Script kiddies on the other hand are prob's where the risk comes from, they generally just rely on social manipulation to steal/guess passwords.


words that are in the english dictionary and are considered "english" are drawn over hundreds of years, they don't just magically pop into the english dictionary whenever someone uses the word, just like ad hominem, not enough people use it to be considered english, i.e + e.g (full phrases) are used a bunch by english people but aren't really english at all, it's all based on how it gets used / is it used by other cultures and what not

so i will say again, ad hominem isn't english, i.e and e.g aren't english and they wont be until we manipulate them into something english and usable, it has to sound english, feel english and be in the english dictionary to be english, i support i.e and e.g being english, but not the actual phrases behind them
I take it they have eightopus's in your local Aquarium(oh noes, aqua is latin again) and you class are political system as a one-man-one-vote-ocrasy ... except for the fact the ocrasy part like the demo part is also greek...


i'm actually just gonna go ahead and say you're at a loss here and all of my tips are right because they're just that; tips
I'm at a loss eh? Good to know... :rolleyes: Sorry to tell you, your confusing the word right and wrong again, you see when a tip is ether an outright lie or just a noobish misunderstanding, we class these as wrong. On the other hand a correct tip, the kind you seemed to avoid, tend to be somewhat more true. :) Hope that clears it up a little.

[Agnostic Bear]

No, that post was stupid you are not understanding me don't worry about it.

[Protege]

I read && as AND and I really || as OR, Its just programmed into my head, soz Danny.