Alternatively, it is possible to use Java's signed integers to emulate unsigned integers of the same size, but this requires detailed knowledge of bitwise operations. If abstracted, function calls become necessary for many operations which are native to some other languages. In all cases, the memory consumed may double, and typically any logic relying on two's complement overflow must be rewritten. While a 32-bit signed integer may be used to hold a 16-bit unsigned value losslessly, and a 64-bit signed integer a 32-bit unsigned integer, there is no larger type to hold a 64-bit unsigned integer. Īlthough it is possible to get around this problem using conversion code and larger data types, it makes using Java cumbersome for handling unsigned data. Unsigned large numbers are also used in a number of numeric processing fields, including cryptography, which can make Java more inconvenient to use for these tasks. Unsigned data is often generated from programs written in C, and the lack of these types prevents direct data interchange between C and Java. Java lacks native unsigned integer types.
Java version 8 introduced some functional programming features. When combined with other features such as function overloading (one verb, multiple nouns) and generic functions (one verb, a family of nouns with certain properties), the programmer can decide whether to solve a specific problem in terms of nouns or verbs. Many other multi-paradigm languages support functions as a top-level construct. Steve Yegge argues that this causes an unnecessary restriction on language expressiveness because a class can have multiple functions that operate on it, but a function is bound to a class and can never operate on multiple types. See also: Object-oriented programming § Criticismīy design, Java encourages programmers to think of a solution in terms of nouns (classes) interacting with each other, and to think of verbs (methods) as operations that can be performed on or by that noun.
0 kommentar(er)
