Okay I just want to start out and say that this is outdated. The only reason why I am posting about this is because I find the history of technology very interesting and I want to share what I’ve read up on. <\/p>\n\n\n\n
<\/p>\n\n\n\n
Alright so, if you’re a programmer you’re probably aware of multiple types of syntax. With Python we have:<\/p>\n\n\n\n
def MyFunction:\n print("Hello World")\n\nMyFunction()<\/code><\/pre><\/div>\n\n\n\nIn Java we have:<\/p>\n\n\n\n
public static void main(String[] args)\n{\n Chicken();\n}\n\nvoid Chicken()\n{\n System.out.println("Hello World");\n}<\/code><\/pre><\/div>\n\n\n\nIn standard C\/C++ we have:<\/p>\n\n\n\n
int main(void)\n{\n printf("Hello World");\n return 0;\n}<\/code><\/pre><\/div>\n\n\n\nBut in the old days we had something called K & R syntax in C. It looked like this:<\/p>\n\n\n\n
int Chicken(a, b, c)\nint a;\nfloat b;\nchar c;\n{\n return 0;\n}<\/code><\/pre><\/div>\n\n\n\nWhat’s interesting about this is that some modern compilers still support this syntax but will scream at you and tell you to not do it. However there’s some important things to note here. Look at the following code block. <\/p>\n\n\n\n
int Chicken(a,b,c)\nint a;\nint b;\n{\n\n}<\/code><\/pre><\/div>\n\n\n\nIf you notice, I never declared the data type for c. By default, the compiler will use integer data types for anything that is undeclared. So the entire concept behind K & R syntax is that you define the function name, and it’s inputs. Then, you define the types of inputs afterwards. It’s very different from what I was taught in university. I just wanted to share this. Hopefully someone finds this interesting. \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
Okay I just want to start out and say that this is outdated. The only reason why I am posting about this is because I find the history of technology very interesting and I want to share what I’ve read up on. Alright so, if you’re a programmer you’re probably aware of multiple types of … <\/p>\n