Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Logic differences in C and Java

People also ask

Is logic same in all programming languages?

All programming languages have one thing in common, the logic for solving a problem remains the same in every language. For instance, if you're designing a calculator, the addition logic will not become a division with the change in language. A regression model built in R will not differ in logic when built in Python.

What is diff bet C C++ and Java?

The C++ language is based on the C language. The Java programming language is based on both C and C++. It is a procedural language. It is an object-oriented programming language.

Do Java and C have the same syntax?

If you are a C or C++ programmer, you should have found much of the syntax of Java--particularly at the level of operators and statements--to be familiar. Because Java and C are so similar in some ways, it is important for C and C++ programmers to understand where the similarities end.

Is Java a logic programming language?

Java annotations and a symbolic Java virtual machine are used to handle the logic programming concepts. In contrast to previous approaches to integrate object-oriented and logic programming, we preserve the syntax of Java. Our language is not split into two distinguishable parts but as closely integrated as possible.


That is because a[index++] = index = index + 2; invokes Undefined Behavior in C. Have a look at this

From the link:

..the second sentence says: if an object is written to within a full expression, any and all accesses to it within the same expression must be directly involved in the computation of the value to be written. This rule effectively constrains legal expressions to those in which the accesses demonstrably precede the modification. For example, the old standby i = i + 1 is allowed, because the access of i is used to determine i's final value. The example

 a[i] = i++

is disallowed because one of the accesses of i (the one in a[i]) has nothing to do with the value which ends up being stored in i (which happens over in i++), and so there's no good way to define--either for our understanding or the compiler's--whether the access should take place before or after the incremented value is stored. Since there's no good way to define it, the Standard declares that it is undefined, and that portable programs simply must not use such constructs. Similar to a[i++]=i (which invokes UB) your expression too invokes UB.

Your expression also has a similar behavior.

The behavior is well defined in Java.