7Units/src/main/java/sevenUnits/utils, branch v1.0.0b2

Ensure LinearUnit&Prefix ==/hash obey contracts

2025-05-31T01:30:44Z

Previously, these classes' equals() and hashCode() methods did not obey the contracts: For equals(), I considered two values equal even if there was a very small deviation, in order to avoid floating-point error. This equals relation is not transitive (i.e. it is possible that a = b && b = c but a ≠ c), violating the contract of equals. This also makes it impossible to properly implement hashCode, as if two values are equal, they must have the same hash code. The solution I had provided is an ineffective hack, which could mess with hash maps and sets. I have changed the implementation to demand exact equality. I have also provided equalsApproximately() methods to both classes that use the old behaviour. Hash codes are only really used for hash maps, and the old implementation doesn't even achieve its purpose, so I did not add a method to return the old hash behaviour.

Throw error on expressions with too many operators

2025-05-31T00:54:18Z

ExpressionParser: use correct operand order

2025-05-31T00:54:17Z

Most of the internal problems with the expression parser happened because I was accepting the arguments for binary operators in the wrong order. For example, '2 - 1' became '1 2 -', not '2 1 -'. The likely cause of this error is the following sequence of events: - In commit 6dbd32cd, I created the code for interpreting RPN. I accepted two arguments from the stack (o1 and o2), then performed o1 o2. However, because stacks are in LIFO order, I should have actually done o2 o1. - Later, in commit 94349688, I created the code for converting an infix expression to RPN. Creating the expressions in the correct order did not work, because my interpreter used the incorrect order. To 'fix' this problem, I created the expressions in the incorrect order. I did not notice any discrepancy, probably because I was not testing the individual methods, only the two-step whole (which found no errors).

Setup automated javadoc

2025-05-18T04:03:29Z

./gradlew javadoc

Add tests for NameSymbol

2025-03-21T20:26:01Z

Allow fractional exponents

2024-08-22T16:45:37Z

Correct encoding of ±

2024-08-15T22:26:34Z

Format source code & set explicit UTF-8

2024-03-24T18:14:11Z

Complete exponentiation of dimensions

2024-03-23T20:29:12Z

Previously, you could only exponentiate individual dimensions in expressions. For example, `Length^3` was valid, but `(Length / Time)^2` was not. This is now fixed.

Bumped version number to 0.4.0b1 & added @since

2022-07-08T17:46:45Z