You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2023. It is now read-only.
Hmm, http://php.net/manual/en/language.types.null.php states:
"There is only one value of type null, and that is the case-insensitive keyword NULL." If it is case insensitive, it shouldn't make a difference I would think.
||||"0/1 instead of false/true is just wrong. 0 and 1 are integers, true and false are booleans""""""
1- dont see that. First check it! get a benchmark with 0/1 - false/true
""""the case for constant is a convention: all constants should be uppercase, except for null, true, and false""""
2- lol. this is YOUR law??
benchmarks are not so useful. It's better to keep a clear, readable, consistent code. Most of cost of a code is related to humans (developers), not to machines (cpu, bandwith, etc.)
I didn't invent any conventions. Just google it around. Of course, you can use whatever you want in your project, but a public project should follow most accepted conventions as much as possible.
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
use ' instead of ", this is faster.
use 0/1 instead of FALSE/TRUE.
Change "null" case to Upper. NULL is constant. type
The text was updated successfully, but these errors were encountered: