Of Brackets, Braces, Parentheses, Slashes and Backslashes

[abajan]

To my knowledge...

these are parentheses: ()
these are brackets: []
these are braces: {}
this is a slash: /
and this is a backslash: \

Yet during my quest over the years to jam my brain silly with as much computing stuff as possible, I’ve noticed that many folk call parentheses “brackets”, brackets “square brackets”, braces “curly brackets” or occasionally “curly braces”, and slashes “forward slashes”. The only one everyone seems to agree on is the backslash.

Just out of curiosity, what do you peeps call these various symbols?

[Cricket]

Originally Posted by abajan

To my knowledge...

these are parentheses: ()
these are brackets: []
these are braces: {}
this is a slash: /
and this is a backslash: \

Yet during my quest over the years to jam my brain silly with as much computing stuff as possible, I’ve noticed that many folk call parentheses “brackets”, brackets “square brackets”, braces “curly brackets” or occasionally “curly braces”, and slashes “forward slashes”. The only one everyone seems to agree on is the backslash.

Just out of curiosity, what do you peeps call these various symbols?

I use almost exactly the same except I specify forwardslash.

[CyberWizard]

I never called braces anything - they are too hard to describe

As far as slashes I would always specify forward or back.

[megamoose]

I call these open and close brackers: ()
Square brackets: []
Curly Brackets: {}
Forwardslash: /
Backslash: \

Suppose it doesn't really matter what they're called and TBH I very rarely feel the need to describe them

[ScriptMan]

To be really honest, it depends on which one I omitted and how long it took me to find it.

On a good day I agree with you.

The missing brace can take the longest. Hence the more colorful names are reserved for it.

I have that missing semi-colon down pat. It is one line above the error code.

[abajan]

Originally Posted by ScriptMan

To be really honest, it depends on which one I omitted and how long it took me to find it.

On a good day I agree with you.

The missing brace can take the longest. Hence the more colorful names are reserved for it.

I have that missing semi-colon down pat. It is one line above the error code.

Now that you mention it, last night I stumbled upon what appears to be a nifty online tool but I’m yet to try it out. (Presently, my code blocks are pretty small and Notepad++’s highlighting features suffice for the time being but others might find BalanceBraces to be useful.)

BTW, thanks for the semicolon tip.

[ScriptMan]

When building nested conditionals where there may be a series of braces I usually test each fragment to make sure it is doing what I want and then tag them as shown below as I construct the script.

if (something isset)
{ // open isset
if a condition
{ // open 1
action line of code
} //close 1

if a condition
{ // open 2
action line of code
} // close 2

} // close isset

In this simple example that seems unnecessary but if you throw in a couple of whiles and elses you start to see the need.

I also frequently have debug routines which are simple echo statements to test the input or post functions.

error_reporting(E_ALL); // debug only
include ("config.php");

/*
echo "The following lines are part of the debug routine.";
echo "<br>";
echo $_POST['date'];
echo "<br>";
echo $_POST['title'];
echo "<br>";
echo $_POST['desc'];
echo "<br>";

*/

That link you posted looks interesting